-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Point-In-Time-Restore #1059
Comments
Hi, V. |
Hi, ;) |
Hi, |
@dcz01 Point-in-Time recovery is possible with many backup integrations that REAR supports (NBU, TSM, DP, NSR, BAREOS, BACULA to name a few). Only the internal backup programs (like tar and rsync) do not support this feature in REAR. |
Regarding full backup and differential backup The current implementation supports only to restore one full backup plus one single incremental backup so that currently "BACKUP_TYPE=incremental" actually implements a differential backup cf. #974 @dcz01 I think it would be best when you implement support I am not a user of "BACKUP_TYPE=incremental" but as far In general regarding issues with the backup: Relax-and-Recover is neither a backup software nor a This means issues regarding the backup usually It is very different to what extent support for each Usually only basic support for the various backup tools This means when a particular backup tool The general basic question is if more and more backup related In general see also |
Well i think i understand it now that i should use and external backup program like tsm for backup and restore and the simply internal backup solution will not be extended with something like that. |
Point-In-Time-Restore
OS_VENDOR=RedHatEnterpriseServer
OS_VERSION=6
What about the idea of restoring with rear to an point-in-time?
So that the user can select or enter an date of point-in-time and the scripts selects the nearest full backup and the last differential backup if the date is not the full backup itself.
The text was updated successfully, but these errors were encountered: