Improve the remote restore description

This commit is contained in:
Bob Mottram 2015-04-10 13:43:45 +01:00
parent 65fd0fddcf
commit 26fb10aced
2 changed files with 55 additions and 47 deletions

View File

@ -54,37 +54,40 @@ freedombone-remote
#+END_SRC
You can then enter the usernames, domains and ssh logins for one or more remote servers. The system will try to backup to these remote locations once per day.
* Restore from a friend
** With a completely new Freedombone installation
This is the ultimate disaster recovery scenario in which you are beginning completely from scratch with new hardware and a new Freedombone installation. It is assumed that the old hardware was destroyed, but that you have the passwords stored within a password manager on a USB thumb drive.
First log in and create a new friends list:
#+BEGIN_SRC bash
ssh username@domainname -p 2222
emacs ~/backup.list
#+END_SRC
Add entries like this. The numbers are the ssh port number to log in on.
#+BEGIN_SRC bash
username1@frienddomain1:2222//home/username1 ssh_password1
username2@frienddomain2:2222//home/username2 ssh_password2
...
#+END_SRC
Save and exit with *CTRL-x CTRL-s* then *CTRL-x CTRL-c*.
Now log in as root and edit the restore script.
Very important is to take a copy of the contents of *backup.key*.
#+BEGIN_SRC bash
su
emacs /usr/bin/restorefromfriend
cat /etc/ssl/private/backup.key
#+END_SRC
Recover your backup password from your password manager and set the PASSPHRASE variable accordingly.
Store it within a password manager on a USB drive which you carry with you. In the worst case scenario you'll be able to restore your system on completely new hardware if you have this key, so long as at least one of your friends servers is accessable via ssh.
* Restore from a friend
** With a completely new Freedombone installation
This is the ultimate disaster recovery scenario in which you are beginning completely from scratch with new hardware and a new Freedombone installation (configured with the same username and domain names). It is assumed that the old hardware was destroyed, but that you have the backup key stored within a password manager on a USB thumb drive.
Save and exit with *CTRL-x CTRL-s* and *CTRL-x CTRL-c*.
First log in and if you don't already have one then create a new friends list:
#+BEGIN_SRC bash
ssh username@domainname -p 2222
freedombone-remote
#+END_SRC
Configure the remote server login details.
Now log in as root and restore the backup key which you have in your password manager.
#+BEGIN_SRC bash
su
editor /etc/ssl/private/backup.key
#+END_SRC
Paste in the backup key, then save and exit.
#+BEGIN_SRC bash
chmod 600 /etc/ssl/private/backup.key
#+END_SRC
Then use the command:

View File

@ -4,7 +4,7 @@
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<title></title>
<!-- 2015-04-10 Fri 13:05 -->
<!-- 2015-04-10 Fri 13:43 -->
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<meta name="generator" content="Org-mode" />
<meta name="author" content="Bob Mottram" />
@ -261,6 +261,21 @@ freedombone-remote
<p>
You can then enter the usernames, domains and ssh logins for one or more remote servers. The system will try to backup to these remote locations once per day.
</p>
<p>
Very important is to take a copy of the contents of <b>backup.key</b>.
</p>
<div class="org-src-container">
<pre class="src src-bash">su
cat /etc/ssl/private/backup.key
</pre>
</div>
<p>
Store it within a password manager on a USB drive which you carry with you. In the worst case scenario you'll be able to restore your system on completely new hardware if you have this key, so long as at least one of your friends servers is accessable via ssh.
</p>
</div>
</div>
<div id="outline-container-unnumbered-4" class="outline-2">
@ -270,54 +285,44 @@ You can then enter the usernames, domains and ssh logins for one or more remote
<h3 id="unnumbered-5">With a completely new Freedombone installation</h3>
<div class="outline-text-3" id="text-unnumbered-5">
<p>
This is the ultimate disaster recovery scenario in which you are beginning completely from scratch with new hardware and a new Freedombone installation. It is assumed that the old hardware was destroyed, but that you have the passwords stored within a password manager on a USB thumb drive.
This is the ultimate disaster recovery scenario in which you are beginning completely from scratch with new hardware and a new Freedombone installation (configured with the same username and domain names). It is assumed that the old hardware was destroyed, but that you have the backup key stored within a password manager on a USB thumb drive.
</p>
<p>
First log in and create a new friends list:
First log in and if you don't already have one then create a new friends list:
</p>
<div class="org-src-container">
<pre class="src src-bash">ssh username@domainname -p 2222
emacs ~/backup.list
freedombone-remote
</pre>
</div>
<p>
Add entries like this. The numbers are the ssh port number to log in on.
</p>
<div class="org-src-container">
<pre class="src src-bash">username1@frienddomain1:2222//home/username1 ssh_password1
username2@frienddomain2:2222//home/username2 ssh_password2
...
</pre>
</div>
<p>
Save and exit with <b>CTRL-x CTRL-s</b> then <b>CTRL-x CTRL-c</b>.
Configure the remote server login details.
</p>
<p>
Now log in as root and edit the restore script.
Now log in as root and restore the backup key which you have in your password manager.
</p>
<div class="org-src-container">
<pre class="src src-bash">su
emacs /usr/bin/restorefromfriend
editor /etc/ssl/private/backup.key
</pre>
</div>
<p>
Recover your backup password from your password manager and set the PASSPHRASE variable accordingly.
Paste in the backup key, then save and exit.
</p>
<p>
Save and exit with <b>CTRL-x CTRL-s</b> and <b>CTRL-x CTRL-c</b>.
</p>
<div class="org-src-container">
<pre class="src src-bash">chmod 600 /etc/ssl/private/backup.key
</pre>
</div>
<p>
Then use the command: