Full backup only copies partial file set

---

stevebower wrote:

Ok I can drag & drop from the share to backup fine, but when I run the backup job & I allow it to delete the orior to running, it creates the same partial folder set as before. Its looking 'consistent', but I can't see the issue

---

I'm not seeing it either, it is a puzzle.

You could try changing the source share from local to remote (using the NAS IP or perhaps 127.0.0.1 as the host), and specify the same credentials you are using in the drag-and-drop.  Perhaps use Windows (SMB) as the protocol, since that is what the drag-and-drop used.

Using the ip & credentials seems to be working. What is the difference between Windows (archive bit) & Windows (Timestamp)?

Cheers

When doing an incremental backup, Windows (timestamp) uses the modification date on a file to determine if it has changed.  The backup job reads the source files (and metadata) but does not modify the source in any way.

Windows (Archive) backs up a file if the archive bit is set on the source - and when the file is copied, it clears that archive bit.  Note the OS doesn't clear the archive bit on its own, the NAS needs to have permissiion to modify the attribute bits.

Generally speaking the timestamp method is more robust.  For instance if you were making two incremental backups of the same source (to different destinations), then with Archive backups  the first backup would clear all the archive bits - so the second backup would therefore not back up anything.