You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Grant Henke (Jira)" <ji...@apache.org> on 2020/12/02 20:17:00 UTC

[jira] [Created] (KUDU-3219) Incremental Restore Feature

Grant Henke created KUDU-3219:
---------------------------------

             Summary: Incremental Restore Feature
                 Key: KUDU-3219
                 URL: https://issues.apache.org/jira/browse/KUDU-3219
             Project: Kudu
          Issue Type: Improvement
          Components: backup
    Affects Versions: 1.13.0
            Reporter: Grant Henke


Currently Kudu supports incremental backup but it doesn't support incremental restore. This is because we can't validate the state of the target tables has gone unchanged since the full backup was applied so the only "safe" thing to do is to apply a full restore plus all the incrementals. It would be nice to add some validation of table state, but a good first step might be to provide the mechanism for incremental restore and document the limitation.

Today in order to restore only new incrementals you would need to set `createTables=false` and a `rootPath` that only contains the incrementals you want to apply. That is more difficult than necessary because it requires alteration to the backup job or manually dissecting the backup root directory structure.

 

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)