Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

bup-on(1) [debian man page]

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

NAME

       bup-on - run a bup server locally and client remotely

SYNOPSIS

       bup on <hostname> index ...

       bup on <hostname> save ...

       bup on <hostname> split ...

DESCRIPTION

       bup on  runs  the given bup command on the given host using ssh.  It runs a bup server on the local machine, so that commands like bup save
       on the remote machine can back up to the local machine.	(You don't need to provide a --remote option to bup save  in  order  for  this	to
       work.)

       See bup-index(1), bup-save(1), and so on for details of how each subcommand works.

       This  'reverse  mode'  operation  is  useful when the machine being backed up isn't supposed to be able to ssh into the backup server.  For
       example, your backup server can be hidden behind a one-way firewall on a private or dynamic IP address; using an ssh key, it can be  autho-
       rized  to  ssh  into  each  of your important machines.	After connecting to each destination machine, it initiates a backup, receiving the
       resulting data and storing in its local repository.

       For example, if you run several virtual private Linux machines on a remote hosting provider, you could back them up to a local  (much  less
       expensive) computer in your basement.

EXAMPLES

	      # First index the files on the remote server

	      $ bup on myserver index -vux /etc
	      bup server: reading from stdin.
	      Indexing: 2465, done.
	      bup: merging indexes (186668/186668), done.
	      bup server: done

	      # Now save the files from the remote server to the
	      # local $BUP_DIR

	      $ bup on myserver save -n myserver-backup /etc
	      bup server: reading from stdin.
	      bup server: command: 'list-indexes'
	      PackIdxList: using 7 indexes.
	      Saving: 100.00% (241/241k, 648/648 files), done.
	      bup server: received 55 objects.
	      Indexing objects: 100% (55/55), done.
	      bup server: command: 'quit'
	      bup server: done

	      # Now we can look at the resulting repo on the local
	      # machine

	      $ bup ftp 'cat /myserver-backup/latest/etc/passwd'
	      root:x:0:0:root:/root:/bin/bash
	      daemon:x:1:1:daemon:/usr/sbin:/bin/sh
	      bin:x:2:2:bin:/bin:/bin/sh
	      sys:x:3:3:sys:/dev:/bin/sh
	      sync:x:4:65534:sync:/bin:/bin/sync
	      ...

SEE ALSO

       bup-index(1), bup-save(1), bup-split(1)

BUP

       Part of the bup(1) suite.

AUTHORS

       Avery Pennarun <apenwarr@gmail.com>.

Bup unknown-																 bup-on(1)

Check Out this Related Man Page

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

NAME

       bup-tag - tag a commit in the bup repository

SYNOPSIS

       bup tag

       bup tag <tag name> <committish>

       bup tag -d <tag name>

DESCRIPTION

       bup tag lists, creates or deletes a tag in the bup repository.

       A tag is an easy way to retreive a specific commit.  It can be used to mark a specific backup for easier retrieval later.

       When  called without any arguments, the command lists all tags that can be found in the repository.  When called with a tag name and a com-
       mit ID or ref name, it creates a new tag with the given name, if it doesn't already exist, that points to the commit given  in  the  second
       argument.  When called with '-d' and a tag name, it removes the given tag, if it exists.

       bup  exposes  the  contents  of	backups with current tags, via any command that lists or shows backups.  They can be found under the /.tag
       directory.  For example, the 'ftp' command will show the tag named 'tag1' under /.tag/tag1.

       Tags are also exposed under the branches from which they can be reached.  For example, if you create a tag named 'important'  under  branch
       'computerX',  you  will	also be able to retrieve the contents of the backup that was tagged under /computerX/important.  This is done as a
       convenience, and should the branch 'computerX' be deleted, the contents of the tagged backup will be available through  /.tag/important	as
       long as the tag is not deleted.

OPTIONS

       -d, --delete
	      delete a tag

EXAMPLE

	      $ bup tag new-puppet-version hostx-backup

	      $ bup tag
	      new-puppet-version

	      $ bup ftp "ls /.tag/new-puppet-version"
	      files..

	      $ bup tag -d new-puppet-version

SEE ALSO

       bup-save(1), bup-split(1), bup-ftp(1), bup-fuse(1), bup-web(1)

BUP

       Part of the bup(1) suite.

AUTHORS

       Gabriel Filion <lelutin@gmail.com>.

Bup unknown-																bup-tag(1)
Man Page