I see server groups as being more useful for load balancing and redundancy. While you can indeed have users on the other systems while you perform the updates, the other servers become nearly unusable as the cache updates, especially for anything other than very minor changes. I've simply had less issues if I simply bring down the other servers during the changes and then bring them back up again after. In my experience, that actually provides a better user experience, because knowing that it's down for a short time is easier to deal with than extremely slow performance during a cache update.
Lyle From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Joe DeSouza Sent: Tuesday, February 24, 2009 1:40 PM To: [email protected] Subject: Re: ARS 7.1 server group issue ** That sort of beats the whole purpose of the whole concept of having server groups though. When working like it should, the secondary servers 'do not know' about the def changes that have occured due to changes made from the primary server, until the new cache on the primary server has been recreated, and the primary server then signals the secondary servers that there has been a change... When properly setup it does work as designed. Anthony, are all your servers in the server group of the same configuration, and running the same applications? What is the physical memory on the servers? Joe ________________________________ From: Lyle Taylor <[email protected]> To: [email protected] Sent: Tuesday, February 24, 2009 2:20:43 PM Subject: Re: ARS 7.1 server group issue ** While AR is supposed to support it, in my experience it is best to shut down everything but the primary server, make your changes, and then bring everything back up again. Things just go more smoothly that way. Lyle From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Anthony K R Sent: Tuesday, February 24, 2009 11:37 AM To: [email protected] Subject: ARS 7.1 server group issue ** Hi, In Remedy server group environment, when the def changes on primary server other servers either throw malloc error ( so the updates not reflected) or crash. Anyone seen this? Env: ARS 7.1 patch 5 with ITSM 7.0 suite Windows 2003 Oracle 10g Thanks, Anthony __Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are" html___ NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
