Moving a collector

this page explains how to move a collector to a new host while maintaining its connection to factry historian moving a collector follows essentially the same steps as docid\ iv4 sd56tdxcqkrkcj4kv , with some additional considerations for token continuity prepare the new host ensure the new host meets the docid\ gq3brw 0i46lgkfuitl3u make sure it can reach the historian server over the required network ports install the collector software following the docid\ iv4 sd56tdxcqkrkcj4kv handling api tokens when generating a new api token for the collector, the old token remains valid for 24 hours this allows the collector to continue sending data during the migration if you still have the old token saved, you do not need to generate a new token to perform the move configure the collector on the new host apply the same configuration as the previous collector instance ensure any environment variables or custom settings are restored on the new host start the collector service it will register with the historian using the token and resume sending data expected outcome after moving a collector the collector runs on the new host data continues flowing to the historian without interruption the collector appears online in the historian under its original instance no duplicate collector instances remain troubleshooting collector does not appear in historian check that the collector service is running on the new host verify that the api token is valid and correctly configured confirm that the historian url and port are reachable from the new host collector stops sending data ensure there are no firewall or network restrictions preventing communication verify that environment variables and configuration files were correctly migrated check collector logs on the new host for errors token expired before migration generate a new api token and update the collector configuration on the new host the collector will reconnect to historian once the new token is applied