Google Drive for Backup & as binded Local Storage

[martinkbs]

@eddowding There are basically two steps:

1. Create the link with rClone with the Drive you want to synchronize the files
2. Mount that drive in a folder on your system so that Cloudron can view it. This is the step that you will surely miss. To do this you just have to run the following command:

rclone mount NAME-UNIT:/ /mnt/backups --allow-other --delete-before

After this step, if you do a ls on the folder //mnt/backups you should already see the files that are in the Drive unit, and therefore you can already link this folder from Cloudron to make the backups. The files in the //mnt/backups folder and the Drive are synced bi-directionally.

If I have a gap this week, I will prepare a small guide with all the steps, because now that I remember, it is necessary to create a small bash and put it in the crontab so that everything continues to work when the server restarts ...

[girish]

@eddowding Looks like you are in the Volumes UI. I don't think this works like that.

(Just my guess) @martinkbs has manually mounted the Google Drive via SSH and then configured it as the backup destination in Backups -> Configure .

[martinkbs]

You are right @girish. The screenshot of @eddowding is the volume interface.

The Configure Backup Storage looks like this:

Although this same procedure is also compatible with Volumes and can be used in applications such as Navidrome, etc.

root@xxxxxxxxx:~# rclone config
Current remotes:

Name                 Type
====                 ====
GDRIVE-MUSIC         drive

e) Edit existing remote
n) New remote
d) Delete remote
r) Rename remote
c) Copy remote
s) Set configuration password
q) Quit config
e/n/d/r/c/s/q>

---

!/bin/bash
/usr/bin/rclone mount GDRIVE-MUSIC:/ /mnt/media/music --allow-other

---

It will also have to be included in the guide...

PS: GDRIVE-MUSIC is a shared drive @robi

[eddowding]

Hmm I had another crack at this, but after I try to mount the drive from the rclone command line, it sits there for ages and does not complete.

I tried mounting and it seems to work (gets a green light) but then a backup errors.

  "taskId": "2441",
  "errorMessage": "Unable to chown:ENOENT: no such file or directory, chown '/mnt/backups/snapshot/app_21c3ed5d-24b5-46a7-afd9-874c5e23e2c8.tar.gz'",
  "timedOut": false,
  "backupId": null

All tips / ideas appreciated.

[eddowding]

One of my mistakes was not leaving the rclone mount command "open". I was expecting it to complete and return a prompt.

Now it's mounted and had a good crack at backing up, but ultimately came back with "copy exited with code 1 signal null"

[eddowding]

see https://forum.cloudron.io/topic/4753/backup-error-copy-exited-with-code-1-signal-null/9

[girish]

@eddowding can you try disabling hard links (the "Use hardlinks" checkbox in the backup configure UI) ? I am guessing hard links are not possible when using this mounted storage. cp tries to use hardlinks when that option is checked.

[eddowding]

@girish Thanks - good tip. I tried it but this time...

So.. who knows?!

Unable to chown:ENOENT: no such file or directory, chown '/mnt/backups/cloudron/snapshot/app_21c3ed5d-24b5-46a7-afd9-874c5e23e2c8.tar.gz'

[bss_]

I am also struggling with drive issue. I had stored some data, my space got filled but data is not there.

[girish]

I have made chown configurable for "mountpoint" provider in 7.1