-Instalation
-===========
+Installation
+============
Doing something very complex in ~100 SLOC_ is not easy, unless you're standing
in the shoulders of giants. I'm standing in the shoulders of rsync_ mainly, so
Providing a ssh_ key
--------------------
-When doing a backup of a remote host, you probably want ssh_ to be able to login
-without providing a password. To do so, you can generate a ssh_ key, copy the
-public key to the target's ``/root/.ssh/authorized_keys`` (or the user that runs
-the backup) and set the Bacap_ configuration variable ``RSYNC_RSH`` to something
-like::
+When doing a backup of a remote host, you probably want ssh_ to be able to
+login without providing a password. To do so, you can generate a ssh_ key using
+``ssh-keygen``, copy the public key to the target's
+``/root/.ssh/authorized_keys`` using ``ssh-copy-id root@host`` (or the user
+that runs the backup) and set the Bacap_ configuration variable ``RSYNC_RSH``
+to something like::
RSYNC_RSH="ssh -i /path/to/priv-key -o NumberOfPasswordPrompts=0"
it if something is wrong with your key, since if you don't use it, rsync_ will
hang asking for a password.
+Also, you may consider using ``StrictHostKeyChecking=no`` ssh option if you
+backup hosts with dynamic IP address.
+
Backup local networks nodes (or nodes with a fast connection)
-------------------------------------------------------------
RSYNC_RSH="ssh -o Compression=no"
-And if your network is trusted, you probably don't need very string encryption
+And if your network is trusted, you probably don't need very strong encryption
either::
RSYNC_RSH="ssh -o Compression=no -c arcfour"