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.

Sign up for GitHub

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

Jump to bottom

Server backup procedure #516

Open
rth opened this issue Apr 30, 2021 · 1 comment
Open

Server backup procedure #516

rth opened this issue Apr 30, 2021 · 1 comment

Comments

@rth
Copy link
Collaborator

rth commented Apr 30, 2021

So think there are 3 main points necessairy to perform a server backup,

Full backup

  1. the PostgreSQL DB, probably with doing an SQL Dump. Currently ~121GB on the main server (but likely many duplicate files).
  2. the ramp_deployment folder (including the submissions). Currently 250GB on the main server. Submissions might not be strictly necessary.
  3. conda envs to facilitate re-deployment. Currently 24GB.

These backups can then be copied into some cloud storage, for instance with rclone

Ideally with encryption, particularly for the DB.

Full backup

The last two points can probably be done incrementally. Less sure about the first one.
@agramfort
Copy link
Collaborator

agramfort commented May 2, 2021 via email

@rth rth mentioned this issue May 12, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@agramfort @rth