Re: [bareos-users] Re: Potential risks when any of the Incremental backups, which has not been yet consolidated got deleted

[Miguel Santos]

If one of the incremental backups is deleted, you will not be able to access the data missing. This will lead to at least 2 issues (that I can think of):

* When you perform a full restore that includes the missing data, it will fail.

* If you try to restore data from that day, it will fail.

If you manage to workaround the dates, restoring data before or after (that does not depend on the data missing), then it is supposed to work.

Although not part of your question, I would ask back, how would someone accidentally delete a volume? If many people have access to the volumes (logical or physical) then you need to modify your environment.

Additionally, any other backup solution will have very similar limitations. It cannot regenerate data that is not there.

On Tue, Feb 27, 2024 at 12:49 PM Руслан Пилипюк <ruslanp...@gmail.com> wrote:

Red square - all backups taken after invalidated backup.
Red X - invalidated backup, that was manually deleted.
Yellow arrow - time when it was noticed during consolidation that incremental backup was deleted

вторник, 27 февраля 2024 г. в 13:47:45 UTC+2, Руслан Пилипюк:

Hey everyone! I was trying to present my company using bareos AI pattern, however I right away got hit with a question -  If any of the incremental backups gets mistakenly manually deleted (by one of the internal workers), what would happen next? Does it mean, that until we notice that someone manually deleted backups would not be taken? And question following that (check diagram) - Does all Incremental backups after that deleted backup, would also be invalidated?

--
You received this message because you are subscribed to the Google Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/6569c1b7-73a0-467a-a2bc-18f812ea376fn%40googlegroups.com.