diff options
| -rwxr-xr-x | README.md | 6 | ||||
| -rwxr-xr-x | TODO.md | 33 |
2 files changed, 37 insertions, 2 deletions
@@ -43,6 +43,8 @@ for your discs: mkfs.btrfs /dev/my_volume_group/byteback echo '/dev/my_volume_group/byteback /byteback btrfs compress 0 0' >>/etc/fstab mount /byteback + chown byteback /byteback + chmod u+w /byteback Finally, before setting up the client, add @@ -56,13 +58,13 @@ Clients are machines that need to be backed up. Assuming you can log into the remote 'byteback' user with a password or administrative key, you only need to type one command on the client to set things going: - byteback-setup-client --destination byteback@mybackuphost.net: + sudo byteback-setup-client --destination byteback@mybackuphost.net: If this goes OK, you are ready to start backing up. I'd advise taking the first backup manually to make sure it goes as you expect. Type this on the client to start and watch the backup. - byteback-backup --verbose + sudo byteback-backup --verbose Configuring byteback-backup --------------------------- @@ -39,3 +39,36 @@ TODO list for byteback * (same for postgres using pg_start_backup() and pg_stop_backup()) +jhackett@bm-jhackett:~$ sudo byteback-setup-client --destination byteback@byteback-server.default.tethra.uk0.bigv.io +No hostname set, using bm-jhackett.bytemark.co.uk + +Skipping key generation, delete /etc/byteback/key if that's wrong +byteback@byteback-server.default.tethra.uk0.bigv.io's password: +/usr/lib/ruby/1.9.1/fileutils.rb:247:in `mkdir': Permission denied - bm-jhackett.bytemark.co.uk (Errno::EACCES) + from /usr/lib/ruby/1.9.1/fileutils.rb:247:in `fu_mkdir' + from /usr/lib/ruby/1.9.1/fileutils.rb:221:in `block (2 levels) in mkdir_p' + from /usr/lib/ruby/1.9.1/fileutils.rb:219:in `reverse_each' + from /usr/lib/ruby/1.9.1/fileutils.rb:219:in `block in mkdir_p' + from /usr/lib/ruby/1.9.1/fileutils.rb:205:in `each' + from /usr/lib/ruby/1.9.1/fileutils.rb:205:in `mkdir_p' + from /usr/bin/byteback-setup-client-receive:30:in `<main>' +*** Remote setup didn't work +jhackett@bm-jhackett:~$ sudo byteback-setup-client --destination byteback@byteback-server.default.tethra.uk0.bigv.io +No hostname set, using bm-jhackett.bytemark.co.uk + +Skipping key generation, delete /etc/byteback/key if that's wrong +byteback@byteback-server.default.tethra.uk0.bigv.io's password: +Create subvolume 'bm-jhackett.bytemark.co.uk/current' +Setup worked! To take your first backup run: byteback-backup --verbose +jhackett@bm-jhackett:~$ sudo byteback-backup --verbose +system: ssh -o BatchMode=yes -o ConnectionAttempts=5 -o ConnectTimeout=30 -o ServerAliveInterval=60 -o TCPKeepAlive=yes -x -a -i /etc/byteback/key -l byteback@byteback byteback-server.default.tethra.uk0.bigv.io byteback-receive --ping --verbose +Permission denied (publickey,password). +*** Could not connect to byteback@byteback@byteback-server.default.tethra.uk0.bigv.io: +jhackett@bm-jhackett:~$ sudo -u ^Cyteback-backup --verbose +jhackett@bm-jhackett:~$ cd /etc/byteback/ +jhackett@bm-jhackett:/etc/byteback$ ls +destination key key.pub +jhackett@bm-jhackett:/etc/byteback$ cat destination +byteback@byteback@byteback-server.default.tethra.uk0.bigv.io +jhackett@bm-jhackett:/etc/byteback$ dpkg -l | ^C + |