[
https://issues.apache.org/jira/browse/HBASE-15862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15317364#comment-15317364
]
Vladimir Rodionov commented on HBASE-15862:
-------------------------------------------
>From MySQL:
{quote}
MySQL:
Full Versus Point-in-Time (Incremental) Recovery
A full recovery restores all data from a full backup. This restores the server
instance to the state that it had when the backup was made. If that state is
not sufficiently current, a full recovery can be followed by recovery of
incremental backups made since the full backup, to bring the server to a more
up-to-date state.
Incremental recovery is recovery of changes made during a given time span. This
is also called point-in-time recovery because it makes a server's state current
up to a given time. Point-in-time recovery is based on the binary log and
typically follows a full recovery from the backup files that restores the
server to its state when the backup was made. Then the data changes written in
the binary log files are applied as incremental recovery to redo data
modifications and bring the server up to the desired point in time.
{quote}
All restores are PIT restores. Others do not make sense. Let us not
overcomplicate stuff and default overwrite mode.
> Backup - Delete- Restore does not restore deleted data
> ------------------------------------------------------
>
> Key: HBASE-15862
> URL: https://issues.apache.org/jira/browse/HBASE-15862
> Project: HBase
> Issue Type: Bug
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Attachments: HBASE-15862-v1.patch
>
>
> This was discovered during testing. If we delete row after full backup and
> perform immediately restore, the deleted row still remains deleted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
