I see.
What I wanted to point your attention was that there could be an option to check the destination somehow. Many use-cases of users involve static destinations where the archives reside.
SB knows when it had made a full archive and during a normal incremental run now it doesn't check the dest and creates its incremental archive, as you suggested. An option in settings could be beneficial to also check destination before creating an incremental/diff archive, and if dest is missing (or changed somehow outside of SB, and by "changed" I mean some lightweight means to check for folder existence or totally empty folder in case of not zipping) then to propose to create full archive instead. That's all.
To be exact - I know if the dest could not be found that being perfectly valid, but SB knows that it had created FULL archive already, no matter where. That's why it is creating the incremental archive in the first place![:)]( "Smile")
.
What I wanted to point your attention was that there could be an option to check the destination somehow. Many use-cases of users involve static destinations where the archives reside.
SB knows when it had made a full archive and during a normal incremental run now it doesn't check the dest and creates its incremental archive, as you suggested. An option in settings could be beneficial to also check destination before creating an incremental/diff archive, and if dest is missing (or changed somehow outside of SB, and by "changed" I mean some lightweight means to check for folder existence or totally empty folder in case of not zipping) then to propose to create full archive instead. That's all.
To be exact - I know if the dest could not be found that being perfectly valid, but SB knows that it had created FULL archive already, no matter where. That's why it is creating the incremental archive in the first place
.