summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPatrick J Cherry <patrick@bytemark.co.uk>2017-03-15 10:25:36 +0000
committerPatrick J Cherry <patrick@bytemark.co.uk>2017-03-15 10:25:36 +0000
commit34746585134c7c47744964ccba96dc550e3faffc (patch)
treec6e6edd278ce1fe852eddd502ebd86ed474a1aec
parent4711690932dc3997cff47d758a2bc593bd243408 (diff)
Update URLs to point at the automatic repos.
Also replaced tabs with spaces ;)
-rw-r--r--README.md34
1 files changed, 17 insertions, 17 deletions
diff --git a/README.md b/README.md
index b1e8897..9038490 100644
--- a/README.md
+++ b/README.md
@@ -16,11 +16,11 @@ Packages
We maintain packages for several releases of Debian GNU/Linux and Ubuntu, which can be found on repository host:
-* http://repo.bytemark.co.uk/byteback/
+ http://repo.bytemark.co.uk/open-source/byteback/
You can install these by creating a file `/etc/apt/sources.list.d/byteback.list` with contents such as the following (which is for the `jessie` release of Debian):
- deb http://repo.bytemark.co.uk/byteback/jessie ./
+ deb http://repo.bytemark.co.uk/open-source/byteback/master/latest/jessie ./
Once you've created the source-file you should be able to install the package via:
@@ -29,7 +29,7 @@ Once you've created the source-file you should be able to install the package vi
If you have never installed a package from the Bytemark repository you can resolve any errors about an unknown GPG via:
- wget -O - https://secure.bytemark.co.uk/key/repositories-2014.key | sudo apt-key add -
+ wget -O - https://secure.bytemark.co.uk/key/repositories-2014.key | sudo apt-key add -
Setting up: server
@@ -41,20 +41,20 @@ You then need to perform the following local setup on the server, which can secu
The following commands are appropriate for a Debian system, you might need to alter them for other Linux distributions, or if you are not using LVM for your discs:
#
- # Create a dedicated UNIX user which will store everyone's backups, and
- # allow logins
- #
- adduser --system byteback --home /byteback --shell /bin/bash
+ # Create a dedicated UNIX user which will store everyone's backups, and
+ # allow logins
+ #
+ adduser --system byteback --home /byteback --shell /bin/bash
#
- # Create a dedicated btrfs filesystem for the user, and add that as its home
- #
- lvcreate my_volume_group --name byteback --size 1000GB
- mkfs.btrfs /dev/my_volume_group/byteback
- echo '/dev/my_volume_group/byteback /byteback btrfs noatime,space_cache,compress=lzo,clear_cache,autodefrag,user_subvol_rm_allowed 0 0' >>/etc/fstab
- mount /byteback
- chown byteback /byteback
- chmod u+w /byteback
+ # Create a dedicated btrfs filesystem for the user, and add that as its home
+ #
+ lvcreate my_volume_group --name byteback --size 1000GB
+ mkfs.btrfs /dev/my_volume_group/byteback
+ echo '/dev/my_volume_group/byteback /byteback btrfs noatime,space_cache,compress=lzo,clear_cache,autodefrag,user_subvol_rm_allowed 0 0' >>/etc/fstab
+ mount /byteback
+ chown byteback /byteback
+ chmod u+w /byteback
Finally, before setting up the client you should add the following to `/etc/ssh/sshd_config`, and restart the ssh-service:
@@ -68,11 +68,11 @@ Install the '`byteback`' package on the client host(s), along with the dependenc
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:
- sudo 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.
- sudo byteback-backup --verbose
+ sudo byteback-backup --verbose
Configuring byteback-backup