[
https://issues.apache.org/jira/browse/HBASE-19108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237083#comment-16237083
]
Vishal Khandelwal commented on HBASE-19108:
-------------------------------------------
This is not only about how the jobs for backup are triggered. These can be done
cron or oozie. Here is the issue is backup process is unaware of couple of
things
1. What is the expected frequency when full backup should run ?
2. What is the expected frequency when incremental should run ?
3. What are backups which can be deleted ?
Above #1-#3 makes sure management of the backups for a longer run in production
is easier. It is not in controller of a human to screw up something.
Even if command is missed or triggered twice, there is no impact on the
cluster. Take an example if full backup is triggered daily it would eat all
space/if incremental backups jobs are not triggered it would not clear any
WALs/management expiring the backup has high cost.
Here ask is backup is aware what are frequencies it needs to run, when should
it expire. so chances of corrupting or misusing anything in real cluster can be
limited.
> Backups should understand the frequency of full and incremental backup
> ----------------------------------------------------------------------
>
> Key: HBASE-19108
> URL: https://issues.apache.org/jira/browse/HBASE-19108
> Project: HBase
> Issue Type: New Feature
> Components: backup&restore
> Reporter: Vishal Khandelwal
> Priority: Major
> Labels: backup
>
> Backup scheduler which figures out tables for which backups are pending and
> executes all required backups.
> In case of failures, this automates required (full / incremental) backup
> execution based on the set frequency. Thus the support to set frequency and
> expire old backups should be added. This will reduce admin overhead.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
