We’ve noticed on our Terminal Server that the Windows Search service is periodically writing large amounts of data (sustained 600,000-1,000,000 B/sec). This was first noticed when our ShadowProtect backups began generating 2-5GB incremental files. We run them every 15 minutes and this is much larger than our typical backup. We tracked the problem down to Windows Search.
This was noticed after rebooting the server. We restarted the WSearch service and things seemed to calm down for a while. Within a couple of days the problem reappeared. Since then we rebuilt the search index and configured to only index Outlook. Again, it seemed to run fine for a couple of days and then we noticed the large incremental backups caused by WSearch.
Our Terminal Server is Server 2012 R2 which is virtualized on an ESXi host machine. We had Widows Search/Indexing up and running without issue long before this problem appeared.