On 07/29/2013 09:52 AM, Tripp Holden wrote:
They need to be removed from both the replication topology and the console as none of the configuration was removed prior to the servers being brought offline.

For console, you can use the console to remove the instances - in the topology view, right-click on the server instance, and select Remove.

For replication, you'll have to remove all of the replication agreements on other servers that point to the server you removed, then you'll have to run the CLEANALLRUV task to clean up any remaining meta-data.

https://access.redhat.com/site/documentation/en-US/Red_Hat_Directory_Server/9.0/html/Administration_Guide/Managing_Replication-Solving_Common_Replication_Conflicts.html#cleanruv


-Tripp


On Mon, Jul 29, 2013 at 10:47 AM, Rich Megginson <rmeggins@redhat.com> wrote:
On 07/29/2013 09:46 AM, Tripp Holden wrote:
Hi guys,

First time posting here.  I recently inherited a 389 environment where two servers were taken down when we moved out of a datacenter and were not properly removed from the directory configuration prior to their removal.  I've read through the remove-ds documentation and it seems to indicate that the command needs to be run from the instance server that is to be removed.  Is there a recommended method for removing non-existent instances?

Removing them from where?  From the replication topology?  From the console?


Thanks!
-Tripp