Hi Raj We've tried several methods - the most control is by releasing code to the designated admin server (in admin only mode) then removing user servers from the load balance pool one at a time and restarting them. That way we control exactly when the server got the latest cache. Obviously adding the servers back one at time to ensure there was no downtime.
Similarly the web servers where removed from the pool and flushed individually. To make the Mid-Tier servers build the cache we logged into via browser and accessed the main forms. We could use pre-load better but at least this method ensured each server got some form of smoke test. For large releases we'd stop the escalations because most big escalations ran at night. This is when the big releases were done as didn't really want big escalation jobs competing for server time. Same for AIE. For smaller releases that was overkill so the process was modified accordingly. That was a well structured HA environment. Releases where always scheduled for the time when the least amount of users were connecting. I don't recall the problem with the view not being created being caused by other users accessing it at the same time. If it were we would have seen that at least on dev and test where releases happen far more often and someone is always playing around with the main forms. Good luck, Jon From: Raj Sent: Tuesday, September 24, 2013 4:55 PM Newsgroups: public.remedy.arsystem.general To: [email protected] Subject: Strategy for Remedy Release & Maintenance ** Hi All, Just wanted to check with experts in here, what steps do they follow during Remedy Release/Maintenance. In the past, we usually used to do our code push during the scheduled window. But lately we been having issues with code push if we are modifying a form and at the same time user is accessing the form. Issue we noticed is the view never gets re-created, in some case we had to re-run the view DDL. Since then we started putting Remedy in Admin-Only mode which has helped us upto some extent but not entirely plus we want to avoid admin only mode as basically it transpires to kind of an outage as users are unable to login. So, wanted to check with you all in here, are there any special steps you take during remedy release or maintenance to perform code push/enhancements/bug fix/features, etc. 1. Is Admin-Only mode always needed? Can we do maintenance without putting Remedy Admin-Only mode? 2. Disable escalations - do you think we can also look into disabling escalation during maintenance and then enable it back. 3. Any other suggestions or recommendations? Please advise. Thanks, Raj _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
