If you're performing image backups, there's no way to exclude folders. The reason is that image backups operate on a disk block level, not a file level, and the block level doesn't directly have any concept of individual files. To be able to exclude folders, you'd have to perform a File & Folder backup instead, but that wouldn't be ideal for a Windows partition. I wrote a more detailed comparison between image vs. F&F backups a while ago here
if you're interested. If I had to guess
, it might be possible for Macrium to support excluding certain files and folders from images of NTFS partitions because the NTFS MFT would help establish a "file to block" mapping of the imaged data, but allowing that might break or at least drastically increase the complexity of some other really handy features that Reflect already has, like Rapid Delta Restore/Clone and BitLocker Live Restore/Clone, since an image backup that had certain content excluded wouldn't contain a complete snapshot of the partition's contents anymore. But that is just a guess. Perhaps Macrium will post here and shed more light on this, since I wouldn't mind having this capability myself -- in fact I ended up partitioning my disk and storing my regular data on the new partition (I don't use the user profile folders much) specifically because I couldn't
do this. The other possibility is that Acronis may be capturing file-level image backups rather than block-level backups, rather like Microsoft's own DISM tool does. That has its advantages in some cases, but it certainly also has its limitations.
In terms of your second question, you might be able to create a manual scheduled task to achieve what you want, but I'm not sure. Looking at triggers available in Task Scheduler, it has native support for running a task at logon, but not shutdown/logoff. If you wanted the latter, you'd probably have to choose "On Event" and then find the Event Viewer event for a logoff. The problem you MAY have though is that too many services may have stopped by the point that a logoff event is written to Event Viewer. Again, I haven't tried to set that up, but if you Google "Windows scheduled task at every logoff", you might find something. For the rest of the task, the configured Action would need to be a Reflect command line for your job, the syntax for which you can derive from here
, and in terms of running it at most once per day, when Reflect is about to run a scheduled task, the logged on user (if any) will see a popup prompt and have the opportunity to cancel it, so that's as close as you can get to limiting the number of backups per day. That would actually be handy for your case if you were restarting in the middle of the day for some other reason and didn't want to wait for a backup, for example, but again I don't know if that will even work based on how logged off your session will be by the time that Event Viewer trigger event would have been written.
Finally, manually created scheduled tasks probably won't show up in the Reflect interface, so your definition file and Reflect's Scheduled Tasks tab will appear to have no scheduled tasks listed -- but the task should still run if set up correctly, and you'll still get log entries under the Log tab.