Rclone Latest Version

[Heartbreak Writhe]

Rcloneis single executable (rclone, or rclone.exe on Windows) that you cansimply download as a zip archive and extract into a location of your choosing.See the install documentation for more details.

The Version Tag is the version that the beta release will becomewhen it is released. You can match the Git Commit Hash up with thegit log. The mostrecent release will have the largest Version Tag and Commit Numberand will normally be at the end of the list.

I came to the forum to ask a question on something else I'm dealing with, then I realized I am using rclone v1.36, when the newest version seems to be 1.52.2, so I figured I would update it first, and only ask my question if the issue persists.

Hello there.

I am working on an application. I am using rclone in application. The version I am using is 1.55.1 . I can't run my application with the 1.56 version that came and I couldn't find a way to downgrade to version 1.55.1. I would be glad if you help me.

To be honest, I would recommend avoiding Google Drive as a backup solution because of this issue and others that users on this forum have encountered. Drive is designed to be used primarily by people and not scripts, and there are restrictions based on this assumption.

the TPS limit (and checkers/transfers) are all set with rclone, not restic

you could set the TPS limit as an rclone environmental variable with

export RCLONE_TPSLIMIT=1

on the command line for example.

For automated backups, restic supports specifying the repository location in theenvironment variable RESTIC_REPOSITORY. Restic can also read the repositorylocation from a file specified via the --repository-file option or theenvironment variable RESTIC_REPOSITORY_FILE.

The init command has an option called --repository-version which canbe used to explicitly set the version of the new repository. By default, thecurrent stable version is used (see table below). The alias latest willalways resolve to the latest repository version. Have a look at the designdocumentationfor more details.

On Linux, storing the backup repository on a CIFS (SMB) share or backing updata from a CIFS share is not recommended due to compatibility issues inolder Linux kernels. Either use another backend or set the environmentvariable GODEBUG to asyncpreemptoff=1. Refer to GitHub issue#2659 for further explanations.

In order to backup data via SFTP, you must first set up a server withSSH and let it know your public key. Passwordless login is importantsince automatic backups are not possible if the server prompts forcredentials.

In order to backup data to the remote server via HTTP or HTTPS protocol,you must first set up a remote RESTserver instance. Once theserver is configured, accessing it is achieved by changing the URLscheme like this:

Depending on your REST server setup, you can use HTTPS protocol,password protection, multiple repositories or any combination ofthose features. The TCP/IP port is also configurable. Hereare some more examples:

Restic can backup data to any Amazon S3 bucket. However, in this case,changing the URL scheme is not enough since Amazon uses special securitycredentials to sign HTTP requests. By consequence, you must first setupthe following environment variables with the credentials you obtainedwhile creating the bucket.

If needed, you can manually specify the region to use by either setting theenvironment variable AWS_DEFAULT_REGION or calling restic with an optionparameter like -o s3.region="us-east-1". If the region is not specified,the default region is used. Afterwards, the S3 server (at least for AWS,s3.amazonaws.com) will redirect restic to the correct endpoint.

Until version 0.8.0, restic used a default prefix of restic, so the filesin the bucket were placed in a directory named restic. If you want toaccess a repository created with an older version of restic, specify the pathafter the bucket name like this:

Certain S3-compatible servers do not properly implement theListObjectsV2 API, most notably Ceph versions before v14.2.5. On thesebackends, as a temporary workaround, you can provide the-o s3.list-objects-v1=true option to use the olderListObjects API instead. This option may be removed in futureversions of restic.

Restic can backup data to an OpenStack Swift container. Because Swift supportsvarious authentication methods, credentials are passed through environmentvariables. In order to help integration with existing OpenStack installations,the naming convention of those variables follows the official Python Swift client:

Once environment variables are set up, a new repository can be created. Thename of the Swift container and optional path can be specified. Ifthe container does not exist, it will be created automatically:

To get application keys, a user can go to the App Keys section of the Backblazeaccount portal. You must create a master application key first. From there, youcan generate a standard Application Key. Please note that the Application Keyshould be treated like a password and will only appear once. If an ApplicationKey is forgotten, you must generate a new one.

As of version 0.9.2, restic supports both master and non-master application keys. If using a non-master application key, ensure that it is created with at least read and write access to the B2 bucket. On earlier versions of restic, a master application key is required.

You can then initialize a repository stored at Backblaze B2. If thebucket does not exist yet and the credentials you passed to restic have theprivilege to create buckets, it will be created automatically:

If GOOGLE_ACCESS_TOKEN is set all other authentication mechanisms aredisabled. The access token must have at least the _write scope. Keep in mindthat access tokens are short-lived (usually one hour), so they are not suitableif creating a backup takes longer than that, for instance.

The program rclone can be used to access many other different services andstore data there. First, you need to install and configure rclone. Thegeneral backend specification format is rclone::, the: component will be directly passed to rclone. When youconfigure a remote named foo, you can then call restic as follows toinitiate a new repository in the path bar in the remote foo:

As a more concrete example, suppose you have configured a remote namedb2prod for Backblaze B2 with rclone, with a bucket called yggdrasil.You can then use rclone to list files in the bucket like this:

In order to start rclone, restic will build a list of arguments by joining thefollowing lists (in this order): rclone.program, rclone.args and as thelast parameter the value that follows the rclone: prefix of the repositoryspecification.

With these options, restic works with local files. It uses rclone andcredentials stored on remotehost to communicate with B2. All data (exceptcredentials) is encrypted/decrypted locally, then sent/received viaremotehost to/from B2.

A more advanced version of this setup forbids specific hosts from removingfiles in a repository. See the blog post by Simon Ruderichfor details and the documentation for the forget command to learn aboutimportant security considerations.

Since restic version 0.14 local and SFTP repositories can be madeaccessible to members of a system group. To control this we have to changethe group permissions of the top-level config file and restic will usethis as a hint to determine what permissions to apply to newly createdfiles. By default restic init sets repositories up to be groupinaccessible.

To make this work we can employ the help of the setgid permission bitavailable on Linux and most other Unix systems. This permission bit makesnewly created directories inherit both the group owner (gid) and setgid bitfrom the parent directory. Setting this bit requires root but since itpropagates down to any new directories we only have to do this privilegedsetup once:

3a8082e126