Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

We need a working, documented backup system for the server #37

Closed
christodewit opened this issue Jan 31, 2017 · 3 comments
Closed

We need a working, documented backup system for the server #37

christodewit opened this issue Jan 31, 2017 · 3 comments

Comments

@christodewit
Copy link

christodewit commented Jan 31, 2017

Can you please spend some time to come up with a plan to ensure we have a proper backup system? Perhaps we can rsync / btsync backups to a filestore on the AIFDR cluster? Also we should document how to go about restoring the running services in the case of total hardware failure / security breach. Including but not limited to:

  • osm.linfiniti.com (for osm downloader) - @timlinux to do
    
  • experimental.inasafe.org (for nightly packages)
    
  • test documentation builds
    
  • live web site
    
  • download site
    
  • blog
    

We can also look at using hetzner backup services though I don't think they provide a big enough storage space. Also we could look at using backblaze - its USD 5 a month with unlimited storage.

@Charlotte-Morgan
See original ticket at inasafe/inasafe#1298 for further discussion.

@gubuntu
Copy link
Collaborator

gubuntu commented Sep 18, 2017

@lucernae the backups are working so we just need the documentation?

@gubuntu
Copy link
Collaborator

gubuntu commented Sep 27, 2017

This issue was moved to inasafe/docker-realtime-orchestration#72

@gubuntu
Copy link
Collaborator

gubuntu commented Sep 27, 2017

This issue was moved to inasafe/docker-realtime-orchestration#74

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants