Union and Encrypt drive with maxium performence

Help and Support
1

Suppose,
I have four remote drives: 10GB, 20GB, 30GB, and 40GB. I want to combine them into a single 100GB remote.

Goals:

  • Top Security: Use the highest level of encryption.
  • Performance: Maximize performance without compromising security.
  • File Handling: When I upload a 70GB file, it should automatically encrypt and split, but still be whole and streamable with rclone mount.

What I Need:

  • Simple config suggestions:
    • Should I use encryption first or union?
    • Consider onion or combine?
    • Sync the four drives into one and then mount?

Looking for a straightforward setup without loops or complex options that might slow things down or reduce security.

Thanks!

2

I would recommend the following setup:

union -> crypt -> chunker

Given that your remotes do not have equal space make sure that all of them support rclone about and your union is using quota relevant policies.

Make sure that you use long enough password and salt (password2).

Encryption does not really impact performance (unless you have some extremely underpowered system).

To split large files between different union members you have to use chunker remote on top of everything.

Share you setup (rclone config redacted) and we can check its details.

3

Why myremote: not recommended in crypt and chunker?

4

Sorry do not understand. Could you please elaborate?

5

in Crypt

Storage> crypt
Remote to encrypt/decrypt.
Normally should contain a ':' and a path, eg "myremote:path/to/dir",
"myremote:bucket" or maybe "myremote:" (not recommended).

Enter a string value. Press Enter for the default ("").
remote> remote:path

in Chunker

Storage> chunker
Remote to chunk/unchunk.
Normally should contain a ':' and a path, e.g. "myremote:path/to/dir",
"myremote:bucket" or maybe "myremote:" (not recommended).

Enter a string value. Press Enter for the default ("").
remote> remote:path
6

There is no real technical reason.

But root directory of many remotes is often used by various different services and mixing for example encrypted and non encrypted content can lead to self inflicted mess.

So this recommendation is rather general (but always works well). If you know what you are doing and have full control of root folder you do not have to use any sub path.

Good example where it is not needed is S3 bucket. And where it is strongly recommended is OneDrive or GDrive.

The best advice you will get if you share your setup. There are too many exceptions and details which differ between different remotes to write some general story (for this you can read all docs). Both crypt and chunker have their quirks... Whatever you decide to do make sure that you start small and test before going "live".

7

Will a small chunk size increase upload speed, or should I make the chunk as big as possible? Since my smallest storage is 10 GB, should I use a 10 GB chunk or set a default of 2 GB? I was considering making a 1 MB chunk, hoping it would increase speed, or would it crash due to running out of memory?

Also, what is the best solution for avoiding the use of a hard drive for cache? I don't want to use a single byte to write on the only SSD I have. I want to rely fully on RAM. I have 16 GB of RAM, and my GNU/Linux system only uses 200 MB of it. With Firefox, it uses 1-1.5 GB. If it matters.

Are referring to config file?

8

yes. remotes are different and have different capabilities and limitations.