backup strategy
oschulte opened this issue · 0 comments
oschulte commented
-
archive: make dump, perhaps store on clarinet
-
infrequent access: store on clarinet mysql (e.g. cross-validation). Or maybe get cs-oschulte03 to use clarinet?
-
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