disk/CPU activity during backup?
how tolerant is ATIH2017 of activity (on the Source HDD and/or of the CPU) during a backup operation?
(I have not enabled "Run the backup only when the computer is idle" for my backup tasks; but thus far I have been ensuring that no applications are running during backups.)
FWIW, my only reference point is that during decades using Norton Ghost I routinely run backups overnight and simultaneously ran multi-hour antivirus scans (which I don't intent to be doing going forward) AND running a bittorrent client which did read/write operations on the Source HDD during a backup operation with perfect results. (I occasionally got messages from Ghost about system resources in use during the backup, but I found those backups were valid anyway. Which I found quite pleasing, since as I said, during the backup my bittorrent client did read/write operations on the Source HDD.
Might I find ATIH2017 equally tolerant of this kind of bittorrent activity on the Source HDD?
What about downloading with a Usenet client (at 20Mbps) onto an Excluded folder on the Source HDD (this is something I never tried during Ghost backups)?
Incidentally, the impact of bittorrent activity on my CPU and RAM is minimal.


- Log in to post comments

Thank you very much, Ian!
I don't know whether I'm more impressed by ATIH2017, or by how priceless this forum is to me.
- Log in to post comments