Skip to content

backup strategy #29

Description

@oschulte
  1. archive: make dump, perhaps store on clarinet

  2. infrequent access: store on clarinet mysql (e.g. cross-validation). Or maybe get cs-oschulte03 to use clarinet?

  3. frequent access but not production: move to bugaboo. e.g.

  • nhl_uai
  • _bn and _ct databases for _std databases

Other points:

  • use single production mysql server
  • always mirror the input data

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions