diff --git a/MANUAL.html b/MANUAL.html index b1e1d2c83..9f2871400 100644 --- a/MANUAL.html +++ b/MANUAL.html @@ -1858,10 +1858,11 @@ y/e/d> y

The modified time is stored as metadata on the object as X-Bz-Info-src_last_modified_millis as milliseconds since 1970-01-01 in the Backblaze standard. Other tools should be able to use this as a modified time.

Modified times are used in syncing and are fully supported except in the case of updating a modification time on an existing object. In this case the object will be uploaded again as B2 doesn't have an API method to set the modification time independent of doing an upload.

SHA1 checksums

-

The SHA1 checksums of the files are checked on upload and download and will be used in the syncing process. You can use the --checksum flag.

+

The SHA1 checksums of the files are checked on upload and download and will be used in the syncing process.

Large files which are uploaded in chunks will store their SHA1 on the object as X-Bz-Info-large_file_sha1 as recommended by Backblaze.

Transfers

Backblaze recommends that you do lots of transfers simultaneously for maximum speed. In tests from my SSD equiped laptop the optimum setting is about --transfers 32 though higher numbers may be used for a slight speed improvement. The optimum number for you may vary depending on your hardware, how big the files are, how much you want to load your computer, etc. The default of --transfers 4 is definitely too low for Backblaze B2 though.

+

Note that uploading big files (bigger than 200 MB by default) will use a 96 MB RAM buffer by default. There can be at most --transfers of these in use at any moment, so this sets the upper limit on the memory used.

Versions

When rclone uploads a new version of a file it creates a new version of it. Likewise when you delete a file, the old version will still be available.

Old versions of files are visible using the --b2-versions flag.

@@ -1894,9 +1895,10 @@ $ rclone -q --b2-versions ls b2:cleanup-test

Specific options

Here are the command line options specific to this cloud storage system.

--b2-chunk-size valuee=SIZE

-

When uploading large files chunk the file into this size. Note that these chunks are buffered in memory. 100,000,000 Bytes is the minimim size (default 96M).

+

When uploading large files chunk the file into this size. Note that these chunks are buffered in memory and there might a maximum of --transfers chunks in progress at once. 100,000,000 Bytes is the minimim size (default 96M).

--b2-upload-cutoff=SIZE

-

Cutoff for switching to chunked upload (default 4.657GiB == 5GB). Files above this size will be uploaded in chunks of --b2-chunk-size. The default value is the largest file which can be uploaded without chunks.

+

Cutoff for switching to chunked upload (default 190.735 MiB == 200 MB). Files above this size will be uploaded in chunks of --b2-chunk-size.

+

This value should be set no larger than 4.657GiB (== 5GB) as this is the largest file size that can be uploaded.

--b2-test-mode=FLAG

This is for debugging purposes only.

Setting FLAG to one of the strings below will cause b2 to return specific errors for debugging purposes.

@@ -2022,6 +2024,11 @@ nounc = true

This will use UNC paths on c:\src but not on z:\dst. Of course this will cause problems if the absolute path length of a file exceeds 258 characters on z, so only use this option if you have to.

Changelog