[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 763
  • Last Modified:

replicas stuck in dying and in new state Novell 6.5 sp7

Replaced a server. New server has new name but the same IP address.

Remove replica from all the replica rings. Some are still dying 24 hours later and the rest are in new state.
SBCSWEB is gone and replaced by SBCS5.
How do I get them to the on state?
/****************************************************************************/
NetWare 1602.00 Directory Services Repair 10551.26, DS 10553.73 
Log file for server ".SBCS5.MHD01" in tree "STEININGER"
Start:  Thursday, April 23, 2009  11:55:28 pm Local Time
Retrieve replica status
 
Partition: .Administration
  Replica: .SBCS3.BERLIN                    4-23-2009 23:42:41
  Replica: .SBCS5.MHD01                     4-23-2009 23:42:40
  Replica: .SBCS1.MHD01                     4-23-2009 23:42:41
  Replica: .SBCS2.Administration            4-23-2009 23:42:36
  Replica: .D01-410.MHD01                   4-23-2009 23:45:30
All servers synchronized up to time:          4-23-2009 23:42:36  
 
Partition: .MHD01
  Replica: .SBCS3.BERLIN                     ********** ********
    Server: CN=SBCSWEB.O=MHD01              4-23-2009 23:55:24  -761 Remote
      Object: O=MHD01
    Server: CN=SBCS2.O=Administration       4-23-2009 23:55:24  -761 Remote
      Object: O=MHD01
    Server: CN=SBCS5.O=MHD01                4-23-2009 23:55:24  -761 Remote
      Object: O=MHD01
  Replica: .SBCS5.MHD01                      ********** ********
    Server: CN=SBCSWEB.O=MHD01              4-23-2009 23:55:22  -699 Remote
      Object: O=MHD01
    Server: CN=SBCS2.O=Administration       4-23-2009 23:55:23  -761 Remote
      Object: O=MHD01
    Server: CN=SBCS3.O=BERLIN               4-23-2009 23:55:23  -761 Remote
      Object: O=MHD01
  Replica: .SBCS2.Administration            4-22-2009 15:17:15
    Server: CN=SBCSWEB.O=MHD01              4-23-2009 23:55:25  -761 Remote
      Object: O=MHD01
    Server: CN=SBCS5.O=MHD01                4-23-2009 23:55:25  -761 Remote
      Object: O=MHD01
    Server: CN=SBCS3.O=BERLIN               4-23-2009 23:55:25  -761 Remote
      Object: O=MHD01
  Replica: .SBCS1.MHD01                     4-03-2009 16:03:24
    Server: CN=SBCSWEB.O=MHD01              4-23-2009 23:55:24  -654 Remote
      Object: O=MHD01
    Server: CN=SBCS2.O=Administration       4-23-2009 23:55:24  -761 Remote
      Object: O=MHD01
    Server: CN=SBCS5.O=MHD01                4-23-2009 23:55:24  -761 Remote
      Object: O=MHD01
    Server: CN=SBCS3.O=BERLIN               4-23-2009 23:55:24  -761 Remote
      Object: O=MHD01
  Replica: .SBCSWEB.MHD01                    ********** ********
    Server: CN=SBCSWEB.O=MHD01              4-23-2009 23:55:22  -699 Remote
      Object: O=MHD01
    Server: CN=SBCS2.O=Administration       4-23-2009 23:55:23  -761 Remote
      Object: O=MHD01
    Server: CN=SBCS3.O=BERLIN               4-23-2009 23:55:23  -761 Remote
      Object: O=MHD01
  Replica: .D01-410.MHD01                   4-22-2009 15:15:34
    Server: CN=SBCS3.O=BERLIN               4-23-2009 23:45:31  -761 Remote
      Object: O=MHD01
    Server: CN=SBCS5.O=MHD01                4-23-2009 23:45:31  -761 Remote
      Object: O=MHD01
    Server: CN=SBCS2.O=Administration       4-23-2009 23:45:31  -761 Remote
      Object: O=MHD01
    Server: CN=SBCSWEB.O=MHD01              4-23-2009 23:45:31  -761 Remote
      Object: O=MHD01
 
Finish:  Thursday, April 23, 2009  11:55:29 pm Local Time
 
*** END ***

Open in new window

0
NJAMHA
Asked:
NJAMHA
1 Solution
 
deroodeCommented:
On each server in your network you should remove the server from all replica rings. Make sure that you have designated a master for each replica.

From TID 3338221:

4. Verify that each replica ring is consistent and valid:
Load DSREPAIR -a | Advanced Options | Replica and Partition Operations | (select each replica one at a time ) | View Replica Ring. If the suspect server exists in the replica ring, select it and press enter, a screen will appear entitled Replica Options: Server . Select the option entitled "Remove this Server from the Replica Ring". This will remove the suspect/crashed server from the replica ring for this partition. This information will synchronize out to the other servers in the replica ring.

This step needs to be completed for each replica that the suspect/crashed server contained.

http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=3338221&sliceId=1&docTypeID=DT_TID_1_1&dialogID=34440894&stateId=0%200%2049053663
0
 
NJAMHAAuthor Commented:
I thought that was what I would wind up doing but you know those warnings they give in the process you want to make sure that is what you should be doing.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now