Netware :- Merging two servers and trees
Discussion
Hi, I've got a pair of Netware 6.5 boxes that were independant on different sites but are now moved back to a single site.
So I need to merge them both on to the same tree.
They currently both have the same tree name ( the co name) but different contexts below that.
On the lan they ping each other but dont see each other I assume this is due to the tree names... The workstations can also only see the one server...
I take it to continue I need to
1) rename one of the trees
2) mege the trees together
3) reset things like prefered servers on some of the workstations
anything else I've missed... I've added servers to a tree before but never merged them
ta
G
So I need to merge them both on to the same tree.
They currently both have the same tree name ( the co name) but different contexts below that.
On the lan they ping each other but dont see each other I assume this is due to the tree names... The workstations can also only see the one server...
I take it to continue I need to
1) rename one of the trees
2) mege the trees together
3) reset things like prefered servers on some of the workstations
anything else I've missed... I've added servers to a tree before but never merged them
ta
G
DO NOT allow the two of them access to each other. If they're on the same network now, separate them immediately. Duplicate tree names is one of the quickest routes to DS corruption.
Once they're apart, run a full health check as per TID 10060600 - http://support.novell.com/cgi-bin/search/searchtid... . Don't be tempted to proceed with anything else until you're sure everything is fine - doing this stuff on trees that have issues can make matters ten times worse.
You then have a few options. You'll need to rename one of the trees anyway, so do that - once you're happy it's healthy, load up DSMERGE and pick "rename tree". It needs to be done on the server that holds the master replica of [Root], although if these are both just single servers then it will be. There are a few implications of doing this - lots of products (esp 3rd party) use the tree name for licencing, and things like ZENworks use the tree name in the workstation manager or agent.
If your top-level containers, the organization ones (O=, etc) are different in the two trees, you can use DSMERGE again to perform this as it's name implies. TID 10011011 describes the process. http://support.novell.com/cgi-bin/search/searchtid...
If you just have data and/or print objects to get across, I'd just use the Server Consolidation and Migration Toolkit (SCMT) which is great for copying data about with trustees intact, doing lots of clever stuff to match up users between trees. It's included in most recent NW service packs, or you can download it from Novell. Docs here: http://www.novell.com/documentation/scmt/index.htm... . If in any doubt about the health of your trees, it's a far less invasive way of doing things.
Clients will mostly be finding the tree and servers via SLP - thus you may need to alter SLP settings on the client, and/or SLP scopes on the server and DCHP options that are being sent out to clients.
Hope this gives you some pointers - as I say, the most important thing is getting those servers apart ASAP.
Once they're apart, run a full health check as per TID 10060600 - http://support.novell.com/cgi-bin/search/searchtid... . Don't be tempted to proceed with anything else until you're sure everything is fine - doing this stuff on trees that have issues can make matters ten times worse.
You then have a few options. You'll need to rename one of the trees anyway, so do that - once you're happy it's healthy, load up DSMERGE and pick "rename tree". It needs to be done on the server that holds the master replica of [Root], although if these are both just single servers then it will be. There are a few implications of doing this - lots of products (esp 3rd party) use the tree name for licencing, and things like ZENworks use the tree name in the workstation manager or agent.
If your top-level containers, the organization ones (O=, etc) are different in the two trees, you can use DSMERGE again to perform this as it's name implies. TID 10011011 describes the process. http://support.novell.com/cgi-bin/search/searchtid...
If you just have data and/or print objects to get across, I'd just use the Server Consolidation and Migration Toolkit (SCMT) which is great for copying data about with trustees intact, doing lots of clever stuff to match up users between trees. It's included in most recent NW service packs, or you can download it from Novell. Docs here: http://www.novell.com/documentation/scmt/index.htm... . If in any doubt about the health of your trees, it's a far less invasive way of doing things.
Clients will mostly be finding the tree and servers via SLP - thus you may need to alter SLP settings on the client, and/or SLP scopes on the server and DCHP options that are being sent out to clients.
Hope this gives you some pointers - as I say, the most important thing is getting those servers apart ASAP.
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff