Just wanted to add my note of thanks for the info in this thread.
However, I’ve tried adding the following line at the top of the exclude.txt on my source NAS: {Edit: fixed… see at bottom}
/DataVolume/shares/Mike_Shared/Pictures (Mirror)/
This folder didn’t exist until now (it is to hold a mirror from my S: drive, which I don’t want to back up again to my second NAS). I put some stuff in the folder, and then ran an existing safepoint backup to update it.
BUT that new folder and the stuff in it appeared on the destination NAS, despite being in an excluded folder.
What am I doing wrong? Does this only work on completely new safepoint, or should it also work on an existing safepoint that is updated on a subsequent run? In other words, are these exclusions read at the time of performing a backup, or at the time of creating the backup job?
EDIT:
just realised that there are other paths to the actual shares, and hence the other two variants included in the examples on the first page. Strange that there are multiple paths. Anyhow, I just included the following single line to catch all such paths:
Mike_Shared/Pictures (Mirror)/
And this works with existing backups BTW.
P.S. is the safepoint backup actually just a mirror? Doesn’t seem like any there is any history or evidence of incremental updates in the destination, so I’m assuming so.