[
https://issues.apache.org/jira/browse/OAK-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Parvulescu updated OAK-1159:
---------------------------------
Attachment: OAK-1159.patch
attaching a first draft.
This will only handle the initial backup scenario (backup to a clean directory
using the latest state of the repository).
I'm attaching this for 2 reasons:
- the patch contains a failing test that needs investigation. I've mentioned
a failure before and it was fixed, but as long as we don't have a test to
verify that, we're pretty much in the dark.
- we have other aspects to clarify like where will this interface live and how
can we already expose this as a first-class citizen in Oak, before getting too
deep into how the incremental backup is supposed to work (which is in the end
just an impl detail of a specific mk)
On this matter I'm assuming that the MongoMK will expose a NOOP (maybe throw an
exception?) but probably there are things to take into consideration there as
well.
> Backup and restore
> ------------------
>
> Key: OAK-1159
> URL: https://issues.apache.org/jira/browse/OAK-1159
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: core, mk
> Reporter: Michael Marth
> Assignee: Alex Parvulescu
> Attachments: OAK-1159.patch
>
>
> We need a way to backup and restore a repository. I was thinking that the MK
> impl could expose an interface for this, as the actual implementation would
> differ quite a bit between e.g. TarMK and MongoMK.
> Also, I think we could leverage the MVCC nature of the MKs and mark a
> specific revision as "the revision to backup" (regardless of ongoing writes).
> That would allow us to prevent the ugly situation in JR2, that we need to
> stop writes for a while to produce a consistent backup.
> The restore in such a scenario would discard revisions that happened after
> said marker (but still made it into the backup).
--
This message was sent by Atlassian JIRA
(v6.1#6144)
