Sysadmin scenario: backup&restore

[jamoore]

See: ​https://github.com/openmicroscopy/ome-documentation/pull/504

The backup/restore instructions in the documentation were wrong. This amounts to a data-loss bug where users could be left with a completely corrupted DB and no way to restore it. This and other similar snippets in the sysadmin documentation will need to be more rigorously (and regularly) tested.

[jamoore]

Kenny / Petr: can either of you see a way forward here?

[pwalczysko]

Suggestions:

• try to upgrade/backup from scratch strictly following the docs regularly
• could be done as part of RC testings
• drawback: this will burden one or more very specific persons with lots of setups, so a bit of the opposite direction than what we are doing now (trying to automatize setups)
• alternative: have a compulsory read of the sysadmin restore/backup docs at
  • either every RC or
  • at every release ?

[pwalczysko]

Sorry, corrected the comment - should be backup/restore instead of deploy.

[jburel]

Petr: probably one to look at during the weekly testing?

[pwalczysko]

I think this would be better served by a Trello card. Created ​https://trello.com/c/TBJiPEg1/97-backup-and-restore-docs-testing. We do not have any sysadmin scenario as such, rather the sysadmin user/group manip in UIs and cmd line import, command line interface and dropbox. This one is pure setup according to docs, so I would close this.

[jamoore]

Closing at Petr's request.