You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2013/12/05 11:56:40 UTC

[jira] [Resolved] (OAK-1159) Backup and restore

     [ https://issues.apache.org/jira/browse/OAK-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Parvulescu resolved OAK-1159.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.13

it looks good. if there are other missing bits, we can track them in dedicated issues.

> 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
>             Fix For: 0.13
>
>         Attachments: OAK-1159-v2.patch, 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)