We have a lot of questions about how Athens uses backups (the .bkp files).
The underlying philosophy:
We believe in zero data loss above all else.
We let user manage their own data.
Questions to answer:
How and when does Athens back up my data?
Where does Athens store the backup files?
Can I delete old backup files?
What is the process of restoring from a backup?
Some context and information that should help answer these questions:
Each backup looks like {TIMESTAMP}-index.transit.bkp . This means the user's db folder will eventually have many backups. This is obviously not space-efficient, and expects users to delete/manage their old backups, but this effectively removes any possibility of data loss. We will eventually come up with other approaches for writing and redundancy that are more performant and space-efficient, but the first principle should be no user data loss, which we've accomplished with this solution.
We have a lot of questions about how Athens uses backups (the
.bkpfiles).The underlying philosophy:
Questions to answer:
Some context and information that should help answer these questions: