Local NCO
I have two production servers and a test server (all running Connection-Enterprise). Is there an easier (and less error-prone) method to clone Profiles, Post-Actions, Probes from one environment to the next.
current method is to copy Blobs on one server to a new name one-per each file and then copy these files to a server with a CLI interface and then recreate the scripts and profiles.
it would be nice to be sure that the profiles on each of the servers had the same structure and requirements.
also is there a better method to switch between servers? currently I'm swapping the directory.rc file and restarting the GUI. Others have separate directories for each console agent. must be a better way to do this?
# 1
For switiching agents between servers - I suppos you could create a script to change the .uce.rc file to the one which has the new agent config in it and restart the agents. This then of course could be pushed out and ran as a job through UCE itself making it easy to swap over multiple agents to a different server....
I would have thought that a better way of producing a clone of a server would be to use the backup feature and restore the backup on the clone server. That way you should get an exact copy of the original with the same structure and profile names and so on.
# 2
if aduva could handle the entire load, I wouldn't need two servers. :~(
it can'tIt craps out. Big Time.
maybe fixed in next release?
when serving more than 90 servers it will either crash or the network and systems will grind to a halt while waiting for the server to complete initialization.
(oh and yes I do have some ideas about spawnning requests to sync up with all the agents at the same time. most sys admins would most likely see the same type of solutions ie only spawn upto threshold number of request at the same time. When the request completes, set off subsequent request to other servers.)
but until that issue is fixed, is there another way to keep the content of two (three or four) servers in sync?
My best effort at a solution would be to make one server a repository for a Knowledge Base and have the other servers update from it, in much the same way that they do for the other knowledge bases.
are there tools for managing sections of local knowledge bases?
# 3
just to clarify: because of the load issue, we have to run multiple servers. We initialized the second server using a backup.
after the fact, is there better methods to keep the two in-sync without having to recreate all the entries by hand.
(we use copies of blobs to provide remote sources for Managed Hosts for scripts)
it would be nice if I could import profiles, configuration files, script files and rpm's w/out having to everything by hand.
[and since I do make a mistake once in a while, the two environment do have different names for the same content. My wrong..]
# 7
that's good.
I didn't see any reference to the product in any of the onsite documentation (or the 3 pdfs with the product) which is the extent of my knowledge.
i expect there will be some followup with support/sales.
again. thank you.
(are there any un-offical tools for local managment of Knowlege Bases and NCO's?if I didn't know about the proxy, there is likly at lot of stuff I don't know about..)
