The basic idea is you do not want single database shared with different ars
versions.
The safe way is to actually stop non admin servers, upgrade the admin
server and then upgrade other servers before starting them.
Here is the relevant text from Install guide.
Upgrading servers already in a server group
To upgrade servers that are a part of a server group, follow these
guidelines:
Stop all BMC Remedy AR System servers except the server that owns the
administrative operation.
To check this, open the Configuration tab on the AR System Administration:
Server Information form. For the administrative server, the Disable Admin
Operations check box is not selected.
Upgrade the server that owns the administrative operation first.
Select the Upgrade option during the upgrade.
Upgrade the other servers in the group next. Select the Server Group (BMC
Remedy AR System database) option.
Do not start the non-administrative servers before performing the upgrade
installation on them.
When upgrading components such as the Approval Server and the Email Engine,
remove the associated server from the server group while performing the
upgrade.
To do this, clear the Server Group Member check box on the Server
Information
form or modify the Server-Group-Member option in the ar.cfg [ar.conf] file
On Thursday, August 9, 2012 8:07:45 AM UTC-7, Leonard wrote:
we are upgrading our 7.5.00 patch3 to patch 8. This is my first time
patching a server group. I was wondering if we have to take the servers
out of the group in order to run the patch.
thanks
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are
