Also, besides the equivalent file on the mid-tier and SmartIT servers, are there any other such files to watch out for? Ones were there's more to it than just replacing the server name in the database (noting that for this use case, it's just the DB that is being copied back, no structural changes are being made to the AR servers).
I went ahead and updated the file with the GUID from prod, and it appears to have worked. The correct records in the CCS and AR System Monitor forms were updated.
1 of 1 people found this helpful
I wouldn't have gone down that road, and I think those IDs should be unique.
You could have left both entries or just deleted the old entry.
You'll see the same problem with your midtier entries. I mean the form is called ARMonitor or something like that.
You should just delete the unwanted entry / incorrect server/Process Type entry from "AR System Monitor" , followed by the FileDeployer process restart. The process will turn up automatically as it is running under armonitor and it shall create the new entry with new GUID on AR System Monitor form and same will be updated/synched in the monitor-<ProcessType>-guid.properties file and associated CCS records. Hopefully there will be Knowledge Article coming soon on things to be taken care of from FileDeployer end when customer opt to go with the DB refresh activity during there upgrades. Thanks