pcahyna
pcahyna
Fedora ships the cron job and systemd job examples as documentation
If the backup is taken after `mkrescue`, one can detect the problem, by running `checklayout` before taking the backup. But if the backup is taken before `mkrescue` (and that's the...
I have been thinking about how to help the user to avoid such inconsistencies. > For internal backup methods we may run what checklayout does > during mkbackuponly to avoid...
Another option would be to embed some files in the rescue image: > Rear is checking some files to update the UUID during the recovery, these files should be embedded...
> When an inconsistent backup is taken with an external backup method > after `mkrescue` there is nothing we can do to detect or avoid that. Some external backup methods...
> TSM is used to backup data, and rear the system (what is expected) Sure, but the question was, is the TSM backup of system files made by invoking `rear...
I believe we should leave this issue open. #2795 introduces detection of inconsistency at recovery time, when it is a bit too late. The proper fix would be to avoid...
Well, this does not look "completed", reopening.
> I have no idea why "rear mkbackuponly" creates a disk layout at all I believe this is needed to determine what gets included/excluded in the backup. > but when...
Your storage layout seems to show that the system disks are not using multipath (LVM sits directly on top of `/dev/sd[a-d]2`, without any multipath devices involved), so I wonder why...