Re: Recovering the master
David Gersic
> What information do I need in order to recover the master server in a
> replica ring?
http://www.novell.com/coolsolutions/feature/15748.html
--
---------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Novell Knowledge Partner http://forums.novell.com
Please post questions in the newsgroups. No support provided via email.
Peter Kuo
> And what breaks if I just delete and recreate the server object without
> going through the reference search/replace first?
All attr values that uses the server object as a reference (instead of the
actual text value). An example is the Home Directory attribute.
--
Peter
eDirectory Rules!
http://www.DreamLAN.com
David Gersic
> Thanks for the pointer. It seems a bit NetWare-focused.
It is, but it's the ideas behind the steps that count. The main one is to
save the references (DN type attributes) so that when you remove the
server object, you have a placeholder object and when you bring the
server back in to the tree you can restore the references from the
placeholder.
> In particular,
> that SRVREF utility requires CALWIN32.DLL.
Well, that would make it Win32 specific, not NetWare specific...
> We're using eDirectory as
> the vault in our IDM install and for LDAP, and that's it. No Netware.
So you have DN references in your IDM driver sets, but I don't think
those reference the NCP server object. LDAP won't care, though you may
have to monkey with the certificates if they get dinged. Should be no big
deal.
Remove the server object. Clean up the replica rings. Make sure all
partitions have a Master. Reinstall the server. Put your replicas back on
it, and you should be good to go.
> And what breaks if I just delete and recreate the server object without
> going through the reference search/replace first?
That'll be specific to your tree, but I don't think you'll find much if
it's an IDM vault tree. Usually it's things like user's "home directory"
that you have to look out for. But a vault wouldn't have any of those
anyway.
David Gersic
>> Remove the server object. Clean up the replica rings. Make sure all
>> partitions have a Master. Reinstall the server. Put your replicas back
>> on
>> it, and you should be good to go.
>
> Thanks!
One other thing, since you mentioned IDM. The server specific attributes
for your driver set and drivers will need to be restored. I use Designer,
so it's easy to just re-deploy the configuration.
David Gersic
> dgersic;1848396 Wrote:
>> One other thing, since you mentioned IDM. The server specific
>> attributes
>> for your driver set and drivers will need to be restored. I use
>> Designer,
>> so it's easy to just re-deploy the configuration.
>
> I thought all that was stored in the tree?
It is, but some of it is flagged as "server specific" so that it doesn't
replicate.
> I can redeploy from
> Designer, but I'll lose the driver and application passwords, latest
> assigned uid and gid numbers, etc.
You shouldn't lose anything by a deploy from Designer. Don't delete
anything, just deploy again. Designer should show you what it's going to
update, then it'll go and do it.