When SourceOne Workers cannot update heartbeat for some time in SourceOne DB, then worker gets marked with unresponsive state which allows worker to be deleted.
If you still have issue, you can open service request with EMC Support and they can help you to remove worker.
If same machine was an native archive server with archive or index roles, then there are some things to watch for e.g. files sitting in message center unpack_area subfolders which would not get processed. Support should be able to help processing those.
If you installed the services properly, and you are a 100% sure that the 'decommissioned' servers aren't performing any jobs anymore. There a few SQL Statements you'll need to execute to clean these servers out of your servers list and Native Archive Connection(s).
RKatwal
2 Intern
•
600 Posts
563
0
Posted August 21st, 2015 00:00
Greeting,
When SourceOne Workers cannot update heartbeat for some time in SourceOne DB, then worker gets marked with unresponsive state which allows worker to be deleted.
If you still have issue, you can open service request with EMC Support and they can help you to remove worker.
If same machine was an native archive server with archive or index roles, then there are some things to watch for e.g. files sitting in message center unpack_area subfolders which would not get processed. Support should be able to help processing those.
Best regards,
Rajan Katwal