Differences

This shows you the differences between two versions of the page.

--- tahoe-lafs [2014/11/05 12:07] – anonymous
+++ tahoe-lafs [2022/05/08 11:42] (current) – external edit 127.0.0.1
@@ Line 6: / Line 6: @@
 ==== What is Tahoe ====
-[[https://tahoe-lafs.org/|Tahoe LAFS]] stands for Least Authority File System. It is a file system and data storage with very interesting features.
+[[https://tahoe-lafs.org/|Tahoe LAFS]] stands for Least Authority File Store. It is a cryptographic key value data store with very interesting features and a filesystem-like overlay:
+  * cryptographic capabilities model which acts like a distributed access control system
+  * erasure-encoding
+  * verified end-to-end crypto
-  * secure
-  * decentralized
-  * fault-tolerant
-  * encrypted
-  * peer-to-peer
 You can use it to host and serve files or for your backups.\\
@@ Line 21: / Line 20: @@
 This page is meant to be a resource of Tahoe knowledge. In the hope of making it as easy as possibly for others to start using it.
-==== Details ====
-A group of servers providing storage is called a **storage grid**.
-Files stored on a grid are split into parts. Each node gets only part of your file. Each part is encrypted as well. To later restore a file you only need a limited number of it's parts. For example you spread parts of your file onto 10 nodes but only three of them are needed to restore it.
-There's all kinds of grids out there. Connecting to them is done through their so called **introducer**. This is necessary since not all nodes might be online all the time.
 ===== Installation (with Tor) =====
-In the installation we configure Tahoe to use Tor. All nodes are hidden services.
+In the installation we configure Tahoe to use Tor. All services are Tor hidden services... such as the Tahoe-LAFS introducer and storage nodes.
 ==== Required Packages ====
@@ Line 102: / Line 94: @@
 ==== Backup Files ====
-TODO
+=== Create Backup ===
+    > tahoe backup <FILE_OR_FOLDER> <ALIAS>:<BACKUP_DIRECTORY>
+Afterwards we can //ls// the new backup folder
+    > tahoe ls <ALIAS>:<BACKUP_DIRECTORY>
+Within it we now see two folders: //Latest// and //Archves//. Let's see what they contain.
+    > tahoe ls <ALIAS>:<BACKUP_FOLDER>/Latest
+    > tahoe ls <ALIAS>:<BACKUP_FOLDER>/Archives
+The //Archive// folder includes further directories with timestamped versions of our backup.
+=== Backup Integrity ===
+Tahoe spreads chunks of our files over different shares. Should too many shares go offline our backup will be lost. This is why we should check it's health on a regular basis. This is done with Tahoe's **deep-check** command.
+    > tahoe deep-check <ALIAS>:<BACKUP_FOLDER>
+The resulting output looks like this:
+    > tahoe deep-check ouralias:bar3
+    > done: 4 objects checked, 4 healthy, 0 unhealthy
+Shares will go offline. And there's also a //happy// threshold (defined in your ''tahoe.cfg''). Keeping our backup above the //happy// threshold is achieved by adding a parameter to the //deep-check// command.
+    > tahoe deep-check --repair <ALIAS>:<BACKUP_FOLDER>
+Shares also have a garbage collection policy. When a file hasn't been accessed for too long it is elligible for removal. This prevents shares from running out of disk space too early.\\
+To keep them alive you to renew their so calles **lease**.
+    > tahoe deep-check --repair --add-lease <ALIAS>:
+    > tahoe deep-check --repair --add-lease <ALIAS>:<BACKUP_FOLDER>
+    > tahoe deep-check --repair --add-lease <ALIAS>:<BACKUP_FOLDER>/<SUB_DIRECTORY>
+=== Restore from Backup ===
+Restoring files involves only a copy.
+    > tahoe cp <ALIAS>: <LOCAL_FOLDER>
+    > tahoe cp <ALIAS>:<FOLDER> <LOCAL_FOLDER>
+    > tahoe cp <ALIAS>:<FOLDER>/<FILE> <LOCAL_FOLDER>
+===== Missing Sections =====
+  * links
+  * capabilities: description, usage, etc
+  * setup your own grid
+  * setup a node and add it to an existing grid