bup-ftp(1) [debian man page]

bup-ftp(1)						      General Commands Manual							bup-ftp(1)

NAME

       bup-ftp - ftp-like client for navigating bup repositories

SYNOPSIS

       bup ftp

DESCRIPTION

       bup ftp is a command-line tool for navigating bup repositories.	It has commands similar to the Unix ftp(1) command.  The file hierarchy is
       the same as that shown by bup-fuse(1) and bup-ls(1).

       Note: if your system has the python-readline library installed, you can use the <tab> key  to  complete	filenames  while  navigating  your
       backup data.  This will save you a lot of typing.

COMMANDS

       The following commands are available inside bup ftp:

       ls [-s] [-a] [path]
	      print the contents of a directory.  If no path argument is given, the current directory's contents are listed.  If -a is given, also
	      include hidden files (files which start with a . character).  If -s is given, each file is displayed with its hash from the bup  ar-
	      chive to its left.

       cd dirname
	      change to a different working directory

       pwd    print the path of the current working directory

       cat filenames...
	      print the contents of one or more files to stdout

       get filename localname
	      download the contents of filename and save it to disk as localname.  If localname is omitted, uses filename as the local name.

       mget filenames...
	      download	the contents of the given filenames and stores them to disk under the same names.  The filenames may contain Unix filename
	      globs (*, ?, etc.)

       help   print a list of available commands

       quit   exit the bup ftp client

EXAMPLE

	      $ bup ftp
	      bup> ls
	      mybackup/    yourbackup/

	      bup> cd mybackup/
	      bup> ls
	      2010-02-05-185507@   2010-02-05-185508@	 latest@

	      bup> cd latest/
	      bup> ls
		(...etc...)

	      bup> get myfile
	      Saving 'myfile'
	      bup> quit

SEE ALSO

       bup-fuse(1), bup-ls(1), bup-save(1), bup-restore(1)

BUP

       Part of the bup(1) suite.

AUTHORS

       Avery Pennarun <apenwarr@gmail.com>.

Bup unknown-																bup-ftp(1)

bup-damage(1)						      General Commands Manual						     bup-damage(1)

NAME

       bup-damage - randomly destroy blocks of a file

SYNOPSIS

       bup damage [-n count] [-s maxsize] [--percent pct] [-S seed] [--equal]

DESCRIPTION

       Use bup damage to deliberately destroy blocks in a .pack or .idx file (from .bup/objects/pack) to test the recovery features of bup-fsck(1)
       or other programs.

       THIS PROGRAM IS EXTREMELY DANGEROUS AND WILL DESTROY YOUR DATA

       bup damage is primarily useful for automated or manual tests of data recovery tools, to reassure yourself that the tools actually work.

OPTIONS

       -n, --num=numblocks
	      the number of separate blocks to damage in each file (default 10).  Note that it's possible for more than  one  damaged  segment	to
	      fall  in	the same bup-fsck(1) recovery block, so you might not damage as many recovery blocks as you expect.  If this is a problem,
	      use --equal.

       -s, --size=maxblocksize
	      the maximum size, in bytes, of each damaged block (default 1 unless --percent is specified).  Note that  because	of  the  way  bup-
	      fsck(1)  works,  a  multi-byte block could fall on the boundary between two recovery blocks, and thus damaging two separate recovery
	      blocks.  In small files, it's also possible for a damaged block to be larger than a recovery block.  If  these  issues  might  be  a
	      problem, you should use the default damage size of one byte.

       --percent=maxblockpercent
	      the maximum size, in percent of the original file, of each damaged block.  If both --size and --percent are given, the maximum block
	      size is the minimum of the two restrictions.  You can use this to ensure that a given block will never damage more than one  or  two
	      git-fsck(1) recovery blocks.

       -S, --seed=randomseed
	      seed  the  random  number  generator with the given value.  If you use this option, your tests will be repeatable, since the damaged
	      block offsets, sizes, and contents will be the same every time.  By default, the random numbers are different every time (so you can
	      run tests in a loop and repeatedly test with different damage each time).

       --equal
	      instead  of  choosing random offsets for each damaged block, space the blocks equally throughout the file, starting at offset 0.	If
	      you also choose a correct maximum block size, this can guarantee that any given damage block never damages more than one git-fsck(1)
	      recovery block.  (This is also guaranteed if you use -s 1.)

EXAMPLE

	      # make a backup in case things go horribly wrong
	      cp -a ~/.bup/objects/pack ~/bup-packs.bak

	      # generate recovery blocks for all packs
	      bup fsck -g

	      # deliberately damage the packs
	      bup damage -n 10 -s 1 -S 0 ~/.bup/objects/pack/*.{pack,idx}

	      # recover from the damage
	      bup fsck -r

SEE ALSO

       bup-fsck(1), par2(1)

BUP

       Part of the bup(1) suite.

AUTHORS

       Avery Pennarun <apenwarr@gmail.com>.

Bup unknown-															     bup-damage(1)