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
will be considered a descendant of the old *name*.
(Thus, you can continually create new datasets with
the same name, and later view the history of that
- dataset to see how it has changed over time.)
+ dataset to see how it has changed over time.) The original data
+ will also be available as a top-level file named "data" in the VFS,
+ accessible via `bup fuse`, `bup ftp`, etc.
-t, \--tree
: output the git tree id of the resulting dataset.
\--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
# OPTIONS
-r, \--remote=*host*:*path*
-: save the backup set to the given remote server. If
- *path* is omitted, uses the default path on the remote
- server (you still need to include the ':'). The connection to the
- remote server is made with SSH. If you'd like to specify which port, user
- or private key to use for the SSH connection, we recommend you use the
- `~/.ssh/config` file.
+: save the backup set to the given remote server. If *path* is
+ omitted, uses the default path on the remote server (you still
+ need to include the ':'). The connection to the remote server is
+ made with SSH. If you'd like to specify which port, user or
+ private key to use for the SSH connection, we recommend you use
+ the `~/.ssh/config` file. Even though the destination is remote,
+ a local bup repository is still required.
-d, \--date=*seconds-since-epoch*
: specify the date inscribed in the commit (seconds since 1970-01-01).
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
is 1 (fast, loose compression)
-# EXAMPLE
-
+# EXAMPLES
+
$ tar -cf - /etc | bup split -r myserver: -n mybackup-tar
tar: Removing leading /' from member names
Indexing objects: 100% (196/196), done.