bup split -b COMMON\_OPTIONS
-bup split \<--noop \[--copy\]|--copy\> COMMON\_OPTIONS
+bup split --copy COMMON\_OPTIONS
+
+bup split --noop \[-t|-b\] COMMON\_OPTIONS
COMMON\_OPTIONS
~ \[-r *host*:*path*\] \[-v\] \[-q\] \[-d *seconds-since-epoch*\] \[\--bench\]
\[\--max-pack-size=*bytes*\] \[-#\] \[\--bwlimit=*bytes*\]
\[\--max-pack-objects=*n*\] \[\--fanout=*count*\]
- \[\--keep-boundaries\] \[--git-ids | filenames...\]
+ \[\--keep-boundaries\] \[\--git-ids | filenames...\]
# DESCRIPTION
\--noop
: read the data and split it into blocks based on the "bupsplit"
- rolling checksum algorithm, but don't do anything with the blocks.
- This is mostly useful for benchmarking. Incompatible with -n, -t,
- -c, and -b.
+ rolling checksum algorithm, but don't store anything in the repo.
+ Can be combined with -b or -t to compute (but not store) the git
+ blobs or tree ids for the dataset. This is mostly useful for
+ benchmarking and validating the bupsplit algorithm. Incompatible
+ with -n and -c.
\--copy
: like `--noop`, but also write the data to stdout. This can be
to the server. This is good for making your backups
not suck up all your network bandwidth. Use a suffix
like k, M, or G to specify multiples of 1024,
- 1024*1024, 1024*1024*1024 respectively.
+ 1024\*1024, 1024\*1024\*1024 respectively.
-*#*, \--compress=*#*
: set the compression level to # (a value from 0-9, where