This option is a TRANSFER RULE, so don’t expect any exclude  side
              effects.

              The  first letter of a units string can be B (bytes), K (kilo), M
              (mega), G (giga), T (tera), or P (peta).  If the string is a sin‐
              gle char or has "ib" added to it (e.g. "G"  or  "GiB")  then  the
              units are multiples of 1024.  If you use a two‐letter suffix that
              ends with a "B" (e.g. "kb") then you get units that are multiples
              of 1000.  The string’s letters can be any mix of upper and lower‐
              case that you want to use.

              Finally,  if the string ends with either "+1" or "-1", it is off‐
              set by one byte in the indicated direction.  The largest possible
              value is usually 8192P‐1.

              Examples:  --max‐size=1.5mb‐1  is  1499999  bytes,   and   --max‐
              size=2g+1 is 2147483649 bytes.

              Note  that  rsync  versions  prior  to 3.1.0 did not allow --max‐
              size=0.

       --min‐size=SIZE
              This tells rsync to avoid transferring any file that  is  smaller
              than  the  specified  SIZE,  which  can  help in not transferring
              small, junk files.  See the --max‐size option for  a  description
              of SIZE and other info.

              Note  that  rsync  versions  prior  to 3.1.0 did not allow --min‐
              size=0.

       --max‐alloc=SIZE
              By default rsync limits an individual malloc/realloc to about 1GB
              in size.  For most people this limit works just fine and prevents
              a protocol error causing rsync to request massive amounts of mem‐
              ory.  However, if you have many millions of files in a  transfer,
              a  large  amount of server memory, and you don’t want to split up
              your transfer into multiple parts, you can increase the per‐allo‐
              cation limit to something larger and rsync will consume more mem‐
              ory.

              Keep in mind that this is not a limit on the total size of  allo‐
              cated memory.  It is a sanity‐check value for each individual al‐
              location.

              See  the  --max‐size  option for a description of how SIZE can be
              specified.  The default suffix if none is given is bytes.

              Beginning in 3.2.3, a value of 0 specifies no limit.

              You can set  a  default  value  using  the  environment  variable
              RSYNC_MAX_ALLOC  using  the same SIZE values as supported by this
              option.  If the remote rsync doesn’t understand  the  --max‐alloc
              option,  you  can  override  an environmental value by specifying
              --max‐alloc=1g, which will make rsync avoid sending the option to
              the remote side (because "1G" is the default).

       --block‐size=SIZE, -B
              This forces the block size used in rsync’s  delta‐transfer  algo‐
              rithm  to  a  fixed  value.  It is normally selected based on the
              size of each file being updated.  See the  technical  report  for
              details.

              Beginning in 3.2.3 the SIZE can be specified with a suffix as de‐
              tailed  in the --max‐size option.  Older versions only accepted a
              byte count.

       --rsh=COMMAND, -e
              This option allows you to choose an alternative remote shell pro‐
              gram to use for communication between the local and remote copies
              of rsync.  Typically, rsync is configured to use ssh by  default,
              but you may prefer to use rsh on a local network.

              If  this  option  is used with [user@]host::module/path, then the
              remote shell COMMAND will be used to run an rsync daemon  on  the
              remote host, and all data will be transmitted through that remote
              shell  connection,