Project

General

Profile

Bug #4

Have a database backup policy

mtjm - about 12 years ago - . Updated over 9 years ago.

Status:
open
Priority:
critical
Assignee:
-
% Done:

0%

Description

It's a generally good thing to have and might encourage contributors to use the trackers, not fearing that their changes will be lost.

History

#2

Updated by fauno about 12 years ago

Michał Masłowski wrote:

It's a generally good thing to have and might encourage contributors to use the trackers, not fearing that their changes will be lost.

Random ideas:

  • Have a postgresql slave somewhere else replicating info (connect them via VPN)
  • Periodically dump databases to .sql files and commit them on a git project
#3

Updated by mtjm over 9 years ago

  • Priority changed from bug to critical

+1 for "Periodically dump databases to .sql files and commit them on a git project" (private, not published one).

We also need to backup all git repos (including /etc) and some more data (to be put in another git repo?), we should backup them by fetching to other repos, not copying the files.

Also available in: Atom PDF