Select processes and trigger backup.
Select processes that is not worked on and trigger backup of all metadata. Backup is performed by external system. Results (success, failure) are reported back to Goobi.
Blueprint information
- Status:
- Not started
- Approver:
- Ralf Claussnitzer
- Priority:
- Low
- Drafter:
- daniel-ehrlich
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Approved
- Series goal:
- Accepted for 1.8
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
1 Backup component listening to process state changes and identifies backup candidates
2 Backup is issued by writing job-file to a file system "job" folder watched by the backup daemon
3 Backup daemon takes over and writes any output into that file for logging
4 After successfully backup, the job-file is moved to an "ok" folder
5 On failure, files are moved to "error" folder
6 Administrator may restart failed backup attempt by putting the file as-it-is back to the "job" folder --> back to (2)
----
• Shall a backup job be generated on every process change?
• Shall the process be blocked until the backup was performed correctly?
• Which database entries have to be backed up?
• How will the data be restored? How will the restore keep track of related objects in the database so that they will be present, the ID points to the correct referred item, and the referred item is not duplicated on restore either?
-- Matthias Ronge, Zeutschel, 2012-07-03
