free
/
freedombone
關注 1
收藏 0
複製 0
程式碼 問題 0 合併請求 0 版本發佈 0 Wiki 活動
瀏覽代碼

Improve the remote restore description

Bob Mottram 10 年之前
父節點
65fd0fddcf
當前提交
26fb10aced
共有 2 個檔案被更改，包括 46 行新增 和 38 行删除
統一視圖 顯示文件統計
  1. 18
    15
      doc/EN/backups.org
  2. 28
    23
      website/EN/backups.html

+ 18
- 15
doc/EN/backups.org 查看文件

54 
 #+END_SRC
 54 
 #+END_SRC
55
55
56 
 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.
 56 
 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.
57 
-* Restore from a friend
58 
-** With a completely new Freedombone installation
59 
-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.
60
57
61 
-First log in and create a new friends list:
58 
+Very important is to take a copy of the contents of *backup.key*.
62
59
63 
 #+BEGIN_SRC bash
 60 
 #+BEGIN_SRC bash
64 
-ssh username@domainname -p 2222
65 
-emacs ~/backup.list
61 
+su
62 
+cat /etc/ssl/private/backup.key
66 
 #+END_SRC
 63 
 #+END_SRC
67
64
68 
-Add entries like this. The numbers are the ssh port number to log in on.
65 
+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.
66 
+* Restore from a friend
67 
+** With a completely new Freedombone installation
68 
+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.
69 
+
70 
+First log in and if you don't already have one then create a new friends list:
69
71
70 
 #+BEGIN_SRC bash
 72 
 #+BEGIN_SRC bash
71 
-username1@frienddomain1:2222//home/username1 ssh_password1
72 
-username2@frienddomain2:2222//home/username2 ssh_password2
73 
-...
73 
+ssh username@domainname -p 2222
74 
+freedombone-remote
74 
 #+END_SRC
 75 
 #+END_SRC
75
76
76 
-Save and exit with *CTRL-x CTRL-s* then *CTRL-x CTRL-c*.
77 
+Configure the remote server login details.
77
78
78 
-Now log in as root and edit the restore script.
79 
+Now log in as root and restore the backup key which you have in your password manager.
79
80
80 
 #+BEGIN_SRC bash
 81 
 #+BEGIN_SRC bash
81 
 su
 82 
 su
82 
-emacs /usr/bin/restorefromfriend
83 
+editor /etc/ssl/private/backup.key
83 
 #+END_SRC
 84 
 #+END_SRC
84
85
85 
-Recover your backup password from your password manager and set the PASSPHRASE variable accordingly.
86 
+Paste in the backup key, then save and exit.
86
87
87 
-Save and exit with *CTRL-x CTRL-s* and *CTRL-x CTRL-c*.
88 
+#+BEGIN_SRC bash
89 
+chmod 600 /etc/ssl/private/backup.key
90 
+#+END_SRC
88
91
89 
 Then use the command:
 92 
 Then use the command:
90
93

+ 28
- 23
website/EN/backups.html 查看文件

4 
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
 4 
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
5 
 <head>
 5 
 <head>
6 
 <title></title>
 6 
 <title></title>
7 
-<!-- 2015-04-10 Fri 13:05 -->
7 
+<!-- 2015-04-10 Fri 13:43 -->
8 
 <meta  http-equiv="Content-Type" content="text/html;charset=utf-8" />
 8 
 <meta  http-equiv="Content-Type" content="text/html;charset=utf-8" />
9 
 <meta  name="generator" content="Org-mode" />
 9 
 <meta  name="generator" content="Org-mode" />
10 
 <meta  name="author" content="Bob Mottram" />
 10 
 <meta  name="author" content="Bob Mottram" />
261 
 <p>
 261 
 <p>
262 
 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.
 262 
 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.
263 
 </p>
 263 
 </p>
264 
+
265 
+<p>
266 
+Very important is to take a copy of the contents of <b>backup.key</b>.
267 
+</p>
268 
+
269 
+<div class="org-src-container">
270 
+
271 
+<pre class="src src-bash">su
272 
+cat /etc/ssl/private/backup.key
273 
+</pre>
274 
+</div>
275 
+
276 
+<p>
277 
+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.
278 
+</p>
264 
 </div>
 279 
 </div>
265 
 </div>
 280 
 </div>
266 
 <div id="outline-container-unnumbered-4" class="outline-2">
 281 
 <div id="outline-container-unnumbered-4" class="outline-2">
270 
 <h3 id="unnumbered-5">With a completely new Freedombone installation</h3>
 285 
 <h3 id="unnumbered-5">With a completely new Freedombone installation</h3>
271 
 <div class="outline-text-3" id="text-unnumbered-5">
 286 
 <div class="outline-text-3" id="text-unnumbered-5">
272 
 <p>
 287 
 <p>
273 
-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.
288 
+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.
274 
 </p>
 289 
 </p>
275
290
276 
 <p>
 291 
 <p>
277 
-First log in and create a new friends list:
292 
+First log in and if you don't already have one then create a new friends list:
278 
 </p>
 293 
 </p>
279
294
280 
 <div class="org-src-container">
 295 
 <div class="org-src-container">
281
296
282 
 <pre class="src src-bash">ssh username@domainname -p 2222
 297 
 <pre class="src src-bash">ssh username@domainname -p 2222
283 
-emacs ~/backup.list
284 
-</pre>
285 
-</div>
286 
-
287 
-<p>
288 
-Add entries like this. The numbers are the ssh port number to log in on.
289 
-</p>
290 
-
291 
-<div class="org-src-container">
292 
-
293 
-<pre class="src src-bash">username1@frienddomain1:2222//home/username1 ssh_password1
294 
-username2@frienddomain2:2222//home/username2 ssh_password2
295 
-...
298 
+freedombone-remote
296 
 </pre>
 299 
 </pre>
297 
 </div>
 300 
 </div>
298
301
299 
 <p>
 302 
 <p>
300 
-Save and exit with <b>CTRL-x CTRL-s</b> then <b>CTRL-x CTRL-c</b>.
303 
+Configure the remote server login details.
301 
 </p>
 304 
 </p>
302
305
303 
 <p>
 306 
 <p>
304 
-Now log in as root and edit the restore script.
307 
+Now log in as root and restore the backup key which you have in your password manager.
305 
 </p>
 308 
 </p>
306
309
307 
 <div class="org-src-container">
 310 
 <div class="org-src-container">
308
311
309 
 <pre class="src src-bash">su
 312 
 <pre class="src src-bash">su
310 
-emacs /usr/bin/restorefromfriend
313 
+editor /etc/ssl/private/backup.key
311 
 </pre>
 314 
 </pre>
312 
 </div>
 315 
 </div>
313
316
314 
 <p>
 317 
 <p>
315 
-Recover your backup password from your password manager and set the PASSPHRASE variable accordingly.
318 
+Paste in the backup key, then save and exit.
316 
 </p>
 319 
 </p>
317
320
318 
-<p>
319 
-Save and exit with <b>CTRL-x CTRL-s</b> and <b>CTRL-x CTRL-c</b>.
320 
-</p>
321 
+<div class="org-src-container">
322 
+
323 
+<pre class="src src-bash">chmod 600 /etc/ssl/private/backup.key
324 
+</pre>
325 
+</div>
321
326
322 
 <p>
 327 
 <p>
323 
 Then use the command:
 328 
 Then use the command: