mirror of
https://github.com/eclipse-sailing-analytics/sailing-analytics.git
synced 2026-10-10 14:20:55 +00:00
Updated amazon ec2 backup strategy (markdown)
This commit is contained in:
1 parent
b3088aaccf
commit
9c85e9da38
1 file changed
+1
-1
@@ -8,6 +8,6 @@ With respect to the available admin resources for this project the aim of a back
|
||||
|
||||
The technology behind our backup solution is based on a customized use of GIT repositories that are located on a central backup server. Each client creates an index of all files to backup and then pushes them to that server. That approach guarantees that we have a full history for each file including diffs for plaintext and that space consumption is kept to a minimum by storing only the differences. In addition to that our tool will split and pack files to save space.
|
||||
|
||||
The central backup server is configured with enough space to hold a large amount of backup data. To be able to also recover data in case of a failure or data loss all repositories are sync'd to a S3 bucket.
|
||||
The central backup server is configured with enough space to hold a large amount of backup data. To be able to also recover data in case of a failure or data loss all repositories are sync'd to a S3 bucket. The following image depicts the current structure. On the left hand you see the instances involved. For each of these instances you see the directories or data stores being backup'd. In addition to that you can see the time each of the backups runs. On the right hand you see the structure of the backup server with separate git repositories for each instance.
|
||||
|
||||
<img src="/wiki/images/amazon/EC2BackupStrategy.jpg" width="100%" height="100%"/>
|
||||
Reference in new issue
Block a user