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
cannot recover on clean install system #2852
Comments
@Hardcore-fs Could you please explain what you did step-by-step as it is not 100% clear to us? |
Used the above. (obviously with an NTFS mount point ..not shown) then which scanned system built the ISO and then built a tar file with an extension of *-f.tar if you go straight into incremental on a CLEAN system, there does not appear to be a "backup.tar.gz" also for sanity....... really... when the system runs the "full backup" it should also at minimum find the "backup.tar.gz" If you comment out the "BACKUP_TYPE=Incremental", then the system DOES create "backup.tar.gz" |
For me a test today "just works" with
where 192.168.122.1 is the host
which results on the 192.168.122.1 host
Then on another new created QEMU/KVM virtual machine
|
Tomorrow I will test how an actual incremental backup |
@Hardcore-fs
only tests for Also
and on my system (openSUSE Leap 15.3) I get today
i.e. for me only the first letter is uppercase. |
Hi, Which i can fix by making 2 runs, as outlined above. Could it be that during the restore, the BACKUP_TYPE=Incremental (capital I) I will check if simply changing the "I" will make it function on restore. That said... SW should not be fooled by case changes, user /system input should be sanitized with forced case before compares. (also what happens if these are running on non English systems...? ) |
An actual incremental backup (cf. above) On my "original system" (cf. above):
On my "192.168.122.1 host" (cf. above):
On my "replacement hardware" (cf. above):
|
One more actual incremental backup On my "original system" (cf. above):
On my "192.168.122.1 host" (cf. above):
On my "replacement hardware" (cf. above):
|
Stale issue message |
Relax-and-Recover (ReaR) Issue Template
Rear 2.7
rocky linux 8.5
VMware fusion.
BACKUP=NETFS
BACKUP_PROG=tar
BACKUP_TYPE=Incremental
FULLBACKUPDAY="SAT"
Went straight into an "incremental" backup
rear -v mkbackup
the first file shows as 2022-08-19-2021-F.tar.gz
But REAR complains it cannot find backup.tar.gz
I have no
NETFS_KEEP_OLD_BACKUP_COPY=y
The text was updated successfully, but these errors were encountered: