Since I posted the message, I have picked up the 3.4 Media Manager's
Administration Guide and Appendix F (pg. 430) states what you are
saying:
after the config changes, use bp.kill_all and restart ltid and initbprd
I guess a reboot will do the same thing. :-)
I guess the confusing part in my question was what we are doing with the
cluster and ACSLS. Basically, ACSLS is in the cluster along with the NBU
master server. The media server is outside the cluster. We are failing
over NBU and ACSLS but not the media server. It's actually pretty neat,
and once we are completed we will have greater uptime on our NBU
environment.
Thanks for your help.
"David A. Chapa" wrote:
> Anytime you make changes to tpconfig, you have to
> stop/start the device mgmt daemon (ltid), otherwise the
> changes will not take affect.
>
> I don't think that really answers your question...can
> you give me a little more detail?
>
> thanks
>
> david
>
> Quoting SimonL <simonl AT tvratings DOT com>:
>
> > David,
> >
> > You are mentioning the tpconfig and I have a question
> regarding this
> > command.
> >
> > We are in the process of setting up a VCS high
> availability NBU cluster
> > with where our media server is outside of the two
> node master
> > server/ACSLS cluster. When we switch between
> production and our test
> > cluster configuration it seems our test media server
> occasionally needs
> > to be rebooted after we go through and change our
> tpconfig settings.
> >
> > If you or anyone else knows why we have to go through
> such drastic
> > measures. Is it because there is an RPC connection
> back to the ACSLS
> > server, and just changing the tpconfig settings will
> not take effect
> > unless we do a reboot or kill the daemons?
> >
> > Thanks
> >
> >
>
> <><><><><><><><><><><><><><><><><><><><>
> David A. Chapa
> Consulting Manager
> DataStaff, Inc.
> 847 413 1144
> http://www.consulting.datastaff.com
> ---------------------------------------
> NBU-LSERV AT datastaff DOT com - Adv. Scripting
|
