ePO and repository question

[inkastinka]

Hey!

At the current time we have just one repository. That to me doesn't seem like a to smart solution. I was wondering if anyone here can give me some tips about setting up a couple of other repoz so if one or more goes down all the machines can still get there updates. Is there anything that I should look out for? problems anyone might have had?

thanks a bunch!

Dave

 

[JimmyZ1]

we use ftp repositories, I have around 200, the only problem I had was the number of ftp connection allowed, but once that was fixed I haven't had any problems.

we're running 3.5 patch1

 

[P3dr0]

we use ftp repositories on unix and ms servers.
I have 30 repositories.
It works perfect, client goes to connect there to make the update, and also product upgrade (vs451 to vs71).
I use epo 301

I have some little problems, but i think they were resolved in the version 3.5 patch 1.

 

[JimmyZ1]

yeah, we had some frameworkservice issues early on, but since that it's been pretty smooth.

 

[inkastinka]

ok just so I understand you guys, I need to have a hell of alot of repozzz? why is this? shouldn't it be enough with 3 - 4 in a normal network....of 500 servers and 2 -2500 clients machines?

 

[mattmsudawg]

I'm running one repository with 2500-3000 clients and I have never had a problem. Remember, if you server goes down, clients will still update b/c they will try the default location and then go to NAI's ftp site.

 

[inkastinka]

I have taken away the FTP fall back. we can't have 2000 machines connecting to nai at the same time.
do any of your machines connect to a DMZ server? whats the best way to set up a repoz there?

 

[mattmsudawg]

None of my machines connect to a DMZ. Just my one ePo server and that's it.

 

[JimmyZ1]

Yeah, we're spread out all over... 200+ sites = 200+ repositories

 

[Windexx]

40k+ clients 8 repos 1000s of sites

Notes:

Careful with the number of repositories as you must begin to worry about replication time and network traffic.

If using IIS secure the server!!!

During rollout time periods run the report that will show the utilization across the repositories as it is very handy on showing repository issues.

Make secondaries the least network cost to the client.

Use a custom port if you aren't too late in the game to do so.

 

[inkastinka]

which report was that?

 

[Windexx]

I run the report that may be found by doing the following...

Reports --> Coverage --> Product Updates by Custom Event Groups --> Enter Value = Repository Activity

You now will receive info for total activity which may be pretty useless. So...go to the "Within" tab and set "Enter Value" = Current Day (or other setting(s) that you like). This report may be saved under another name so you may run it quickly without filtering in the future.

Hope this helps