[
https://issues.apache.org/jira/browse/MARMOTTA-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Frank updated MARMOTTA-276:
---------------------------------
Issue Type: New Feature (was: Task)
> Implement a Backup/Restore infrastructure
> -----------------------------------------
>
> Key: MARMOTTA-276
> URL: https://issues.apache.org/jira/browse/MARMOTTA-276
> Project: Marmotta
> Issue Type: New Feature
> Components: Platform
> Reporter: Sebastian Schaffert
> Assignee: Sebastian Schaffert
> Fix For: 3.2
>
>
> Currently it is very difficult backing up all system data and restoring it in
> a new instance. This would be very useful for version upgrades, for moving
> from staging to production servers, etc.
> Backup/Restore could be implemented by a generic backup service that provides
> basic infrastructure for storing the backup data and restoring it, and an
> interface that every component can implement to store its own data. Instances
> of this interface can then be injected via CDI.
> The components would at least provide the following backup functionalities:
> marmotta-core:
> - backup each context/named graph into an RDF file (e.g. Turtle), except the
> volatile contexts (reasoning, caching)
> - backup the system configuration (Configuration Service) into a properties
> file
> marmotta-reasoner
> - backup all reasoning programs; when restored, the programs need to be
> re-evaluated on the triple store
> Other components need to be checked. Versioning information does not need to
> be backed up (it would also be difficult).
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
