[
https://issues.apache.org/jira/browse/OAK-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13838933#comment-13838933
]
Jukka Zitting commented on OAK-1159:
------------------------------------
The latest changes fixed the duplicate-size issue seen above. The results are
now:
{noformat}
$ java -jar oak-run-0.13-SNAPSHOT.jar tarmk repository
Apache Jackrabbit Oak 0.13-SNAPSHOT
TarMK repository
Total size:
69MB in 301 data segments
729MB in 4462 bulk segments
Available for garbage collection:
0kB in 0 data segments
0MB in 0 bulk segments
$ java -jar oak-run-0.13-SNAPSHOT.jar backup repository backup
Apache Jackrabbit Oak 0.13-SNAPSHOT
$ java -jar oak-run-0.13-SNAPSHOT.jar tarmk backup
Apache Jackrabbit Oak 0.13-SNAPSHOT
TarMK backup
Total size:
57MB in 239 data segments
729MB in 4460 bulk segments
Available for garbage collection:
0kB in 0 data segments
0MB in 0 bulk segments
{noformat}
I also tested incremental backups and restoring the repository from a backup.
Both worked as expected.
> 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)
