Aller au contenu principal

If destination not available, then next backup is always a FULL backup?

Thread needs solution

 

If the backup destination is not available when the backup is scheduled, then after reconnecting the destination and choosing 'retry', the next backup is always a FULL backup, not a differential...

Is this expected?

I have selected the standard chain version option.

0 Users found this helpful

I think it has to do that cause its not intelegent enough to see that a chain has not been broken, but simply missed via shedular, and maybe just clone the previous and rename it with a new date.

Hello, Dude1234.

Thank you for reporting the issue! A bug report has been sent to the development team.