Another thought: Since at least Windows 7 (maybe earlier) Windows has included the ability to schedule tasks.
I would suggest scheduling a version of the backup that includes the "/l" parameter and writes to a log file. Run that once a day or however often you like. You can then consult that log file to see if anything needs to be done. If not, ignore it. If something does need to get backed up, you can then manually kick off the backup job without the "/l".
Of course, you can also schedule the backup to just run without the "/l" but that can be asking for trouble. I've learned the hard way that I really don't want the computer deleting files behind my back because something can go wrong with the source drives, which causes Windows to think all the originals are gone and results in it dutifully deleting the backups!
I would suggest scheduling a version of the backup that includes the "/l" parameter and writes to a log file. Run that once a day or however often you like. You can then consult that log file to see if anything needs to be done. If not, ignore it. If something does need to get backed up, you can then manually kick off the backup job without the "/l".
Of course, you can also schedule the backup to just run without the "/l" but that can be asking for trouble. I've learned the hard way that I really don't want the computer deleting files behind my back because something can go wrong with the source drives, which causes Windows to think all the originals are gone and results in it dutifully deleting the backups!
There are probably differences I've never needed to notice, but it seems to work exactly like Linux's rsync, which is what I use for most of my stuff.
