Backups can already be done with
http://code.google.com/p/rapla/issues/detail?id=338
Backups happen when rapla starts and every hour, but could be changed to once
a day (with a configurable time) and at start time, though some users don't
want to rollback one whole day.
The archiver could instruct the file operator to add a timestamp when doing a
backup. During backup all backups that are no longer needed (history can be
configured) are removed.
The archiver could also ask the file operator for a directory list with backup
files and present the user with that list.
With that and a cleverly configured timestamp policy, one could setup a second
rapla application context in jetty e.g. rapla_archive using a different
database but the same data file and could load an archived state e.g. 1 month
ago or 1-10 years ago with all the old resources and reservations, but without
burdening the current rapla installation and without using any command line
tools.
Original issue reported on code.google.com by christop...@gmail.com on 5 Oct 2013 at 6:20
Original issue reported on code.google.com by
christop...@gmail.com
on 5 Oct 2013 at 6:20