I am considering BareOS to replace our R1Soft CDP Backup system. I have some confusion about how backup jobs are merged in bareos compared to our current solution.
Goal In case of a system failure, we need to be able to restore the data exactly the same as it was in the most recent backup point. Current Solution In our current solution, the most recent backup job is an exact replica of the server at the time of the backup. If we browse the files, they are exactly as they were on the server at the time of the backup. So to restore an exact copy, we just pick a restore point and the data is exactly as it was during the time of that backup. Bareos Behavior Using the webui, if I try to restore a job (incremental) and have the file/job merge options selected, I see all files that were on the server since the last full backup. This includes files that were deleted prior to the last job (incremental backup). Is there a way to mimic our current solution? We do not want to restore previously deleted files that were not on the system at the time of the last backup. Perhaps this is not doable with a file-based backup system. Our current solution is a block-based backup. There's a kernel module that keeps track of block changes and sends them to the backup server. Thanks in advance. This is a great tool. The current goal is to use it to backup EC2 instances so we have data out of the AWS environment. -- 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 [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
