[
https://issues.apache.org/jira/browse/GEODE-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240992#comment-16240992
]
ASF subversion and git services commented on GEODE-3801:
--------------------------------------------------------
Commit 81377bb9eef3f46fb282a52d557dd1d9b12ccc6e in geode's branch
refs/heads/GEODE-3801-backup-hardlinks-recommit from [~nreich]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=81377bb ]
GEODE-3801: Use hardlinks for backup oplog files (#963)
* Oplog files that are backed up are read-only. For this reason,
they can be transfered to the backup location through hard links,
instead of copying the file. This change improves speed of backups.
If the creation of a hard link fails, we revert to the existing copy
behavior.
* During backups, the copying of the oplog's krf file was being done while
that file could still be in the process of writing. This change ensures
that if a krf is to be written, that it is finished and included in the
backup
* cleanup existing oplog tests
> Utilize hard-links to copy files during backups
> -----------------------------------------------
>
> Key: GEODE-3801
> URL: https://issues.apache.org/jira/browse/GEODE-3801
> Project: Geode
> Issue Type: Sub-task
> Components: persistence
> Reporter: Nick Reich
> Assignee: Kirk Lund
>
> Instead of copying files which are read-only during a backup, create a
> hard-link to the file in the backup location. This prevents losing the file
> if the original location is deleted, but does not require make a new copy of
> the file. If hard-links cannot be created, revert to the existing copying
> mechanic.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
