jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Parvulescu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-1159) Backup and restore
Date Mon, 02 Dec 2013 15:21:37 GMT

     [ 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-v2.patch

attaching v2 of the patch.

still open issues:
 - incremental backup is not efficient, still needs investigation
 - the file size defaults to 256mb, this can generate rather large backups for small repositories

> 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-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)

Mime
View raw message