@trevortymchuk

Files are removed from the system by the program requiring multiple authenticators. More than one person with their own passwords or other type of human verification. No single individual should be able to remove a artifact from the archive.

---

Does something like this already exist?

I will have to write this up as a blog post.

Comments and suggestions for improvements welcome.

Thanks

part6

#archives #storage #digitalartifacts

@trevortymchuk

The system lives to make sure there are three identical copies of each file locally, offsite backups are updated, and the hardware is good.

Should not require a database. Just the filesystem.

Files are added to the system by copying them onto a hard drive.

part5

#archives #storage #digitalartifacts

@trevortymchuk

Versions of the files on different files are checked against each other frequently. Differences are notified.

In case of drive failure a new drive can be swapped in. Three drives would have to go bad at the same time to lose a file.

So, automated offsite backups of each file in three places.

part4

#archives #storage #digitalartifacts

@trevortymchuk

So after pondering on this I have a solution. This is not a spec. Just a description.

A computer attached to an array of drives. The sole purpose of the system is to maintain archival backups of digital artifacts for instance a set of flac files.

All of this should be automated with an open source program.

Every file exists on at least 3 drives. this is checked frequently.

part3

#archives #storage #digitalartifacts