Basically see if thingworx can check the dates of DB backup in the folder of pc2 and on the thumbdrive check to see if it is successful or is the thumbdrive bad and need replaced. Perhaps a little redundancy by copying over the db backup folder to pc1. Maybe have thingworks check and see if remoteserver.log is over a certain size or any of the databases especially FMDW which is always oversize. Perhaps have thingworx download the mdl weekly and run the ‘update drugs table.exe’ on start up before launching SQ CI?
What about changing the way the master drug list is updated? If it can have an index that shows whats already populated on the list, then when updating it can just grab what isn't there already or what the index shows has changed and rather than updating all 16000 it just grabs the new or changed and finish much sooner.
Checking for backups on PC2 would require an agent of pc2, but could be very possible for single pc's moving forward. It could be implemented for dual pc's if we put an agent on the 2nd pc and associated the same serial number to the asset.
The remote serverlog being larger than xxx file size is a great alarm potential. We are working the symptom of high CPU percentage and this is one of the corrective action/inspection to resolve the issue.