Yes, that's true.
But again - we know we are creating a non-full archive. We know we have already created a full archive for this profile. About half of the use cases (I guess) involve always-accessible destinations.
In this case SB could just memorize for each profile the folder/zip file where the last full archive went. And some new option in program settings to allow to check this too, before a nono-full archive creation. This would give a level of increased confidence in many scenarios where the dest is always accessible, even when not always accessible but accessible at the time the current backup is run (external drive or flash thumb where the full and incr/diff archives are kept - it Is accessible so SB could save the current archive).
Anyway, I tried, and it's up to you to agree or disagree![;)]( "Wink")
.
But again - we know we are creating a non-full archive. We know we have already created a full archive for this profile. About half of the use cases (I guess) involve always-accessible destinations.
In this case SB could just memorize for each profile the folder/zip file where the last full archive went. And some new option in program settings to allow to check this too, before a nono-full archive creation. This would give a level of increased confidence in many scenarios where the dest is always accessible, even when not always accessible but accessible at the time the current backup is run (external drive or flash thumb where the full and incr/diff archives are kept - it Is accessible so SB could save the current archive).
Anyway, I tried, and it's up to you to agree or disagree
.