Highlighted
Absent Member.
Absent Member.
334 views

Subordinate Refernces - Edirectory


Okay, as stated in earlier posts, I am no expert with edir, although I
can do some advanced tasks, however, I Still do not understand
subordinate reference...I have a server that I'm worried about right
now, they are doing construction next door to its server room, and we
have been having power issues. I think the server is at risk, as a
result, I want to remove all of the replicas from it...it has 30
replicas on it right now...I clicked on the server, and in its container
in Edirctory, and proedded to do a test delete of one of the replicas
off this server..I removewd one of the smaller replicas from this
server...I immedatly ended up with a SR object to that
replica....Obviously it is referecing something else....Sooo..my
question is now what...When I right click on this replica, I notice this
is the sic replica creted..Master obvious holds my first and master
replica of the one I deleted...Then the other ones are read/write, Since
master will of course stay on the master, should I have starting at
replica number 2 (The first read/write, should I have been deleteing
them down this way? starting at number two?


--
Techlord
------------------------------------------------------------------------
Techlord's Profile: https://forums.netiq.com/member.php?userid=4035
View this thread: https://forums.netiq.com/showthread.php?t=46617

Labels (1)
0 Likes
5 Replies
Highlighted
Absent Member.
Absent Member.

Re: Subordinate Refernces - Edirectory

On Wed, 23 Jan 2013 17:14:02 +0000, Techlord wrote:

> .I immedatly ended up with a SR object to that replica


Subrefs are managed by eDirectory - you don't need to add/remove them
(and in fact with the normal admin tools, you /can't/ - don't be using
dsrepair or other server based tools as admin tools - use ConsoleOne/
iManager to do admin tasks).

Subrefs are pointers to allow a server holding a parent partition to find
the child partitions it doesn't actually hold.

The purpose is to provide a "replica" attribute (which contains the list
of servers that hold replicas and the replica type) so the server can
walk "down" the tree (ie, away from [root]).

Jim

--
Jim Henderson, CNA6, CDE, CNI, LPIC-1, CLA10, CLP10
Novell Knowledge Partner
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Subordinate Refernces - Edirectory


Put simply, any server that has a M, RW or RO replica of a partition
will get a SR of that partition's children. This is to maintain tree
consistency and is automatically handled by eDirectory, there's nothing
you need to do about SRs.

So when you removed that replica, the server must have held a replica of
that partition's parent so an SR was required. When you remove that
parent the SR will go too.

The only consideration about them is when performing partition
operations, you need to make sure the SRs have completed their Add or
Delete operations as well as the main partition involved, before you
proceed to the next operation.


--
ataubman
------------------------------------------------------------------------
ataubman's Profile: https://forums.netiq.com/member.php?userid=301
View this thread: https://forums.netiq.com/showthread.php?t=46617

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Subordinate Refernces - Edirectory

You may want to consider removing replicas of the top partitions first,
then move down the tree. Doing so you will avoid adding S/R replicas of
the lower partitions since the parents will already be gone before
removing the children.

Good luck.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Subordinate Refernces - Edirectory


ab;224460 Wrote:
> You may want to consider removing replicas of the top partitions first,
> then move down the tree. Doing so you will avoid adding S/R replicas
> of
> the lower partitions since the parents will already be gone before
> removing the children.
>
> Good luck.


Thanks you all once again, and indeed it has a replica of its parent
container (In this case [ROOT]) so indeed, this is where the SR is
coming from..This makes MUCH more sense now, My structure looks like
this:

ROOT
|
O=TopORg
|_ou=School1
|_ou-school2 and onwards

This particular partition had ROOT as a recplica, as well a the replica
of a lower OU so indeed ROOT was looking for its child and put an SR
there 😉 Thanks for pointing out that works 😉

Adam Sander, "That's your home! Can't you see that's your home!!" 😉 -
I don't know why, but how the "SR" works reminds me of that...


--
Techlord
------------------------------------------------------------------------
Techlord's Profile: https://forums.netiq.com/member.php?userid=4035
View this thread: https://forums.netiq.com/showthread.php?t=46617

0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Subordinate Refernces - Edirectory

On Wed, 23 Jan 2013 17:14:02 +0000, Techlord wrote:

> Okay, as stated in earlier posts, I am no expert with edir, although I
> can do some advanced tasks, however, I Still do not understand
> subordinate reference...


Subrefs are pointers. They are created automatically, when needed, and
removed when not.


> I have a server that I'm worried about right
> now, they are doing construction next door to its server room, and we
> have been having power issues. I think the server is at risk, as a
> result, I want to remove all of the replicas from it...it has 30
> replicas on it right now...


If you're worried about the server, I'd recommend moving it to a better
location, not making a bunch of structural changes to your tree.


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.