[
https://issues.apache.org/jira/browse/GEODE-3799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16293444#comment-16293444
]
ASF subversion and git services commented on GEODE-3799:
--------------------------------------------------------
Commit 6c49506ea16e9fe516effe1c15cf33435afb5a1d in geode's branch
refs/heads/feature/GEODE-3781 from [~nreich]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=6c49506 ]
GEODE-3799: Move backups towards a pluggable architecture (#1109)
* This effort decouples the definition of files to be backed up
from the destination of the backup. It will allow for the
development of different, pluggable, strategies for conducting
backups, such as compressed archive files of backups or backup
to cloud providers.
* A new BackupDestination interface is provided and the existing
logic for saving a backup to the filesystem has been moved into
an implementation of this interface, FileSystemBackupDestination.
During a backup, all files are copied to a temporary directory
and added to a definition of the backup. This definition is then
used to send the files to their ultimate destination. In the
current case of moving the files to a specified location on the
filesystem, this is implemented by moving the files from the
temporary location to the target backup directory.
> Create plugin system for specifying where a backup is stored
> ------------------------------------------------------------
>
> Key: GEODE-3799
> URL: https://issues.apache.org/jira/browse/GEODE-3799
> Project: Geode
> Issue Type: Sub-task
> Components: persistence
> Reporter: Nick Reich
> Assignee: Nick Reich
> Fix For: 1.4.0
>
>
> The current logic merges the moving/copying of files with the determining of
> what to backup. To make it possible to store a backup in cloud storage or
> other locations, we need to separate these concerns, putting the variable,
> location-based logic, into a plugin architecture.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
