Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Multiple Notifictaion Servers

Created: 31 Mar 2009 • Updated: 21 May 2010 | 9 comments

Hey,
Can anyone point me to any articles/documentation on setting up an environment with multiple NS's that are quite distant from each other, geographically speaking?

Thanks,
Dan

Comments 9 CommentsJump to latest comment

jharings's picture

is available in KB41981 - Design and Scalability Guide.

Are you looking at this for v7 or still v6? Any specific concerns?

Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.

Shobud's picture

is available in KB41981 - Design and Scalability Guide.

Are you looking at this for v7 or still v6? Any specific concerns?

Not really, just wasn't sure how it all fit together. For example, I didn't realize that every NS had to have it's own SQL database, how inventory forwarding works, can we get away with just deploying Package Servers etc
Stuff like that :-)

This is still for v6.

Dan

Shobud's picture

One quick question.
Package Servers only handle packages created in SWD, yes?
This cannot be used as an alternate location for patches?

Dan

bgreen's picture

Package Servers can replicate any and all files that will be sent from the Notification Server down to the clients, including patches.

Files sent up from the clients (inventory, status, etc) are sent directly to the Notification Server.

KSchroeder's picture

Hey Dan,
We have 5 NSes (NA, EA, AP, 2x LA) WITH 1200 - 18,000 clients.  Regional sites have links from 128K to 20Mbit+, 15 - 180 sites per NS.  Unless you have a LOT of clients, one NS should do.

Thanks,
Kyle
Symantec Trusted Advisor

For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.

jharings's picture

to the forwarding server can sometimes be a bit dicey. I tried to forward inventory at different times during the day. You could cut down the dataclasses being forwarded, to only those required for your reporting needs.

Package servers can't be shared amonst different NS, and NS6 doesn't have anything close (unless you count package replication solution) to NS7's replication and heirarchy.

That being said, I'm a proponet of having lots of package servers.

Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.

KSchroeder's picture

are that there are always some of them down and needing attention.  Maybe it is just our setup (~80% of our PS are workstation-class desktop machines running XP at small sites) but it is hard to keep on top of them and keep them all up.  Maybe it is worse for us since the majority of ours are in some small site out in the middle of nowhere (i.e. farm country) where the power stability is not the best.  Dunno.  But we have replaced at least 30 hard drives and a few power supplies and system boards in our PS fleet in the US.

Thanks,
Kyle
Symantec Trusted Advisor

For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.

Shobud's picture

Thanks for all the replies! I'll be back with more questions later :-)

Actually, before I go away...

Am I right in understanding that with NS6 I can setup Package Servers at each regional site and the clients/agents will grab the patches from these servers and not our NS here in Ottawa?

Dan

jharings's picture

The sites and subnets should be setup first, and then package servers will be assigned to them. This works best if you can import the sites from AD.

Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.