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
Initial support for multiple restore archives (issue1069) #1071
Initial support for multiple restore archives (issue1069) #1071
Conversation
Now I re-implemented differential backup, cf. For my first tests now differential backup In particular I annihilated the RFC 1925 6a indirection Now incremental/differential backup works plain and simple This has the advantage that the admin can change Furthermore I made FULLBACKUPDAY an array so that |
Regardless that for me it works well currently, |
Furthermore I have to adapt the meanwhile outdated The current behaviour is documented only in default.conf. |
Finally I have to improve the messaging |
…he error messaging command and showing the previous comand that lead to the error message is not worth the complicated effort, see http://stackoverflow.com/questions/6109225/bash-echoing-the-last-command-run
…eral weekdays a full backup can be triggered.
…options_commands ' in a script (070_set_backup_archive.sh).
Tested again in several ways and usual backup I think the general approach with using Therefore I will merge that major change now |
See #1069
I introduced the new RESTORE_ARCHIVES() array that
contains the restore input files for 400_restore_backup.sh
I did major changes in 400_restore_backup.sh
so that it now launches a separated restore subshell together
with the progress stuff for each element in RESTORE_ARCHIVES.
Together with changes in 070_set_backup_archive.sh
it does now already restore real incremental backups
(i.e. one full backup plus several incremental backups).
For example assume during several "rear mkbackup"
the backup directory contains:
then "rear recover" will restore those backups:
i.e. the latest full backup plus all incremental backups
afterwards.
The "rear recover" output looks then like (excerpt):
Note that when the backup archive is very small
the current progress stuff in 400_restore_backup.sh
(I did not change its behaviour) does not show
any "Restored ... MiB [avg ... KiB/sec]" message
because it waits initially one second and during that
one second the restore had already finished.