AniNIX::Aether \\ Backup and Failsafe System
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
DarkFeather 49f9f6d315
Standardizing round 1
8 months ago
examples Restructured to better break up backups and add user control 2 years ago
tests Standardizing round 1 8 months ago
.gitignore Standardizing round 1 8 months ago
LICENSE Standardizing round 1 8 months ago
Makefile Standardizing round 1 8 months ago
PKGBUILD Standardizing round 1 8 months ago
README.md Standardizing round 1 8 months ago
aether-gen.bash Restructured to better break up backups and add user control 2 years ago
aether.bash Fixes for makefile and aether.bash -- deduplicate the right files. 4 years ago
make-user.bash Converting to Git 4 years ago
remote-backup Recent dev 3 years ago

README.md

The Aether project is a way to back up server configuration, source code, and file lists to remote locations. These remote locations should be securely controlled by the same administrative staff as the server owner.

Etymology

The Aether project is the AniNIX’s implementation of the “cloud.” While its admins consider the computing cloud to be Computers Living On Unknown Datacenters, aka. with unknown controls and thereby insecure, distributing backups to many locations makes the AniNIX more resilient.

Dictionary.com translates Aether as the Greek personification of the clear sky, and this project lives a wide array of locations across the nebulous Internet, giving it no physical form to hold onto.

Installing

You have two options to install this project:

  • Arch Linux and related distros: Run makepkg -sri
  • Other operating systems: Run make install

Initial setup

To create the aether and aether.pub files, run “make keys”. This should not be repeated.

Adding backup configurations

Individual projects wanting to be backed up by the Aether system should add a file to their package into /usr/local/etc/Aether/backups/.

Relevant Files and Software

Aether installs a script for rsync-based remote backups. We implement this policy through the two 4TB hard-drives, at least one of which is always off-site, that can be plugged into the Maat hotswap bay along with a virtual machine that mounts the ArchLinux iso and the drive in the bay.

Available Clients

The only client is direct server access on one of the client nodes.

Equivalents or Competition

Equivalent services are DropBox, Google Drive, or Barracuda.

Notes

Those deploying Aether should maintain a nodeslist file that only root can read.