Could you assist with Rclone & Gdrive Cache/Crypt configuration?

I have been wanting to setup rclone and gdrive’s cache and crypt folders for some time to start creating a form of “backup” or archiving method for both Plex and in general to create a form of cold storage space for my NAS backups.

For the Plex servers, I have read some guides already, specifically this (rclone posting) and (see below for other guide - new user limitation)

My configuration is a little different in that the storage that I am downloading to is shared over SMB and my plex machine and automation machines are on separate boxes, like below

(see next post for photo)

My config is below:

rclone log

cat ~/.config/rclone/rclone.conf
type = drive
scope = drive
token = {“access_token”:“omit”,“token_type”:“Bearer”,“refresh_token”:“omit”,“expiry”:“2019-03-02T04:25:32.595915343Z”}

type = cache
remote = gdrive:media
plex_url = https://plex.localnet:32400
plex_username = omit
plex_password = omit
chunk_size = 1G
chunk_total_size = 32G
info_age = 2d

type = crypt
remote = gcache:
filename_encryption = standard
directory_name_encryption = true
password = omit
password2 = omit

For an initial testing mount (before I move on to the real deal) I am trying this within my home folder on my NAS using the following commands:

commands run

andrew@nas:~$ rclone mount --allow-non-empty --allow-other --cache-db-purge gcache: ~/mnt/gdrive &
[1] 11498
andrew@nas:~$ echo “this is a test” > ~/mnt/gdrive/test.txt
andrew@nas:~$ cat ~/mnt/gdrive/test.txt
(omit plex error thrown)
this is a test

I can see a folder now called media in my Google Drive but not on the team drive as I specified during the configuration setup. I also can’t seem to run both the gcrypt and gcache at the same time, though I am not fully sure this is supposed to be done this way.

But I would love to make sure I am getting the most out of this.

I am guessing I need to do the following:
(can’t post two images in the thread due to spam restrictions)

To have this setup correctly? I would really appreciate any assistance you could give.

Fuse file systems are brand new to me, and so is rclone. The rest of this docker some of the other plex automation, etc comes pretty naturally, but this topic I have never dealt with, so just not sure where to begin. I am also not sure if gdrive is setup correctly due to the lack of the team_drive working properly.I am specifically looking to encrypt the files I am uploading to GDrive just as a heads up.

As the non-Plex part, I would like to use this as a way to do a cold storage backup and then use my local NAS as a way to do an on-site cache instance. Or something of that sort, are there any existing stories, guides, blogs, that I can read to get an idea of this configuration and learn the pros and cons of it?

this (bytesized) is the other site that I am using as a guide.

Is this the way I will need to setup my configuration?

I can’t quite figure out what you are trying to do. Do you have 2 separate servers you are trying to join together as I think that’s the SMB mounts? I would try to step back and simplify as mixing SMB and rclone isn’t a good idea as it’s tough to troubleshoot.

Sorry if that second photo was confusing, I didn’t remove the SMB mount links.

So I have three separate machines, an automation machine (downloader and sonarr/radarr), plex, and a NAS.

Ideally, the goal is to have the automation machine grab the episodes and store them locally at first (this is by SMB mount), and then when verification is finished, it migrates them to gdrive/gcache/gcrypt.

Then it is automatically made available to Plex once the transfer/upload is done. I would prefer to use Team Drive for this so that I have everything associated with a single “logical” volume. Whether I want to encrypt this or not is up for debate to me still, but I guess that it is easily fixable one way or the other.

On the server archival purpose, encryption is not necessary, but, I am just looking to setup a way to synchronize an entire folder (>18TB) of data automatically. It can be run once a month or something if necessary, but, ultimate goal is to constantly keep it backed up in case of drive failure.