Robert,
 
There used to be a white paper for doing this on the Support site.   You will
have to make a couple of changes to your config file on each server.  Also,
you will have to give each server the same alias name so that when workflow
is sent out with links, they are not dependent upon which server in the group
sent it out.  
 
Also note that if you are on ARS 7.0.1 you will have to wait until patch 2 is
released.  All previous 7.0.1 version have floating licenses issues with
Server Groups.
 
Ed White
Ohio State University Medical Center
Remedy Administrator

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Lammey, Peter A.
Sent: Thursday, April 05, 2007 12:47 PM
To: [email protected]
Subject: Re: Question about server group setup


** 
You will also need to make sure that you add entries in the AR System Server
Group Ranking form.
In here you need entries for all operations used by the AR Server and you
need to specify the server that will be the primary server for that
operation.
 
For example, only one server should process escalations so in this form you
need two entries with the operation "Escalation" and you need to indicate
which server has a Rank of 1 and which has a Rank of 2.
 
There are a number of other operations you need to add to this form as well
depending on what operations you have enabled (we dont use Reconciliation
Engine for example).
 
Besides this you also need to fill in the Server Group Name in the Server
Information dialog in the Admin tool (in the Advanced Tab at the bottom).
 
Surprised BMC never mentioned these steps but I believe they are necessary.


Thanks 
Peter Lammey 
ESPN MIT Technical Services & Applications Management 
860-766-4761 

 

________________________________

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Halstead, Robert
Sent: Thursday, April 05, 2007 12:32 PM
To: [email protected]
Subject: Question about server group setup


** 
We are going to create a server group for our production environment
including 2 servers.
 
Currently our users connect via the server remedy.domain.com, if we create
our server group as remedy, with they still be able to use remedy.domain.com
or do that have to modify it?
 
And just as a sanity check, I want to see if we are good on our steps for
this migration. I've spoken with BearingPoint a few times on this...as well
as BMC, but something doesn't feel right:

Are we forgetting anything on our move to a server group?
 
Here are the steps:
1) backup remedy database
2) stop remedy services on primary application server blnmt001svrmd
3) startup remedy service on secondary application server
4) patch secondary server to match primary server
5) shutdown secondary application server
6) copy all change management/approval and flashboard directories to
secondary server
7) startup remedy services on both primary and secondary services
8) create server group in remedy admin tool and add both servers
9) apply server group licenses in admin tool
10) make modification to DNS
11) make modification to Load Balancer
 
Can anyone comment on this please?
 
Thank you,
 

Bob Halstead                             
Advanced Services                         "The superior man cannot be known
in little matters, 
Bresnan Communications                   The small man may not be entrusted
with great concerns, 
Billings, Montana                                 but he may be known in
little matters."

__20060125_______________________This posting was submitted with HTML in
it___ __20060125_______________________This posting was submitted with HTML
in it___ 

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to