NS 7.0 - Parent / Child - Replication Software Management

sscheube's picture
sscheube
April 14th, 2009

Hello everyone,

I am trying to set up an NS 7.0 pilot containing two NS where the parent should replicate everything to the child NS. Now I am facing some difficulties with the Software Management.

I have created some "Software Releases" within the Software Catalog and I added a "Package" within that "Release". The Package Source is set to "Access package from a directory on the Notification Server" and the Package Location is something like D:\packages\....

So far so good this package was properly created on the parent NS however It does not get created (shared) on the child NS even though I can see it in the "Software Catalog". I have read somewhere in the documentation that you have to copy the "physical files" manually which I did but for example the share which is then used for the distribution is not getting created.

Has anyone the same problem? Or can someone help me configuring this correctly?

Thanks
Stefan

Filed under: , , , , , ,
0 votes
BBishop's picture
BBishop
28 weeks 5 days ago

Child NS

Have you set up a package server for the child NS?  I believe packages are only replicated to package servers, not to the NS server itself, even though the packages on the Parent NS are located on the server.

I just wanted to get this out there quick so I am not 100% certain.  I will check and let you know.

0 votes
jSmudge's picture
jSmudge
28 weeks 3 days ago

Please post the answer when

Please post the answer when you find it Brent (good to see you're still kicking around!!).  :-)

This was a major concern of mine when first looking at NS7. I didn't want the source replicated around to every NS (just to all the PS's). It makes no sense to copy the files to the Child NS's, if you ask me - - especially if you use a UNC location of your DSL for the source of the "package", just pull it from the UNC to the PS's.

0 votes
sscheube's picture
sscheube
28 weeks 3 days ago

PS Setup / Site Config

Actually we always had the two package server set up because the hierarchy cannot be implemented if both child and parent not have a package server each.

However in the end the problem was just that the Site was not configured correctly. What we forgot in the first place was that we forgot to assign the PS to a site. We only assigned the subnet which was not enough. This was not really easy to find out because there is not really a step by step instruction how it should be done.

0 votes