AOMEI Backupper Pro problem with Differential Backup schedule
Set up a scheme for Full + 3 Differential backups. Problem is that after first full backup the next 3 backups should be differential but I am getting full backups if no data has changed? Shouldn't the differential backups be very tiny if no data has changed? Instead it creates a full backup every time.
Why?
Why?
Tagged:
Comments
It seems that the backup always fails when the automatic schedule triggers (unattended of course), but will have no problem if I open Backupper and run the scheme from inside Backupper. So a new question, why does the scheduled backup always fail as shown in the last image below?
and here is the scheme...
Finally here is the log showing the failed scheduled backup on 10/13/2023 which should have been a differential (but shows as Full) and also failed.
It almost seems like the scheduler does not have the credentials to access the NAS when the scheduled date/time occurs. I have checked the credentials in the backup task for the NAS target and it is correct (also NAS access works fine when I test it in Backupper ).
I'm using the built-in AOMEI scheduler service (not the Windows 10 task scheduler), could this be an issue with the built-in AOMEI scheduler service?
As for 4103, please make sure that your network is stable and in good condition.
It just happened again: I made a full backup last night,
then attempted to make a differential backup this morning,
but got another full backup. I used Version 7.3.2.
Yes it has failed three weeks in a row now (my schedule is weekly). But as I said the backup WILL run fine if I start from within Backupper and manually run it.
I have checked the NAS, it is accessible and I can successfully backup from inside the Backupper program.
The problem seems to be with the scheduled backup, it just fails whenever it is triggered by the scheduler.