I'd have to agree....if you don't have two identical setups front-ended by a 
load
Balancer then you won't have a true complete failover if one fails. A well 
designed
System should provide total transparency to users in case of the failure of 
one....
I would like to see BMC come out with a more complete white paper or 
documentation 
On what has to be done in detail though....


-----Original Message-----
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Ramey, Anne
Sent: Thursday, March 19, 2009 1:58 PM
To: [email protected]
Subject: Re: Installing Secondary Server in Server Group

Actually, that could cause problems if one server goes down.  The other won't 
be able to correctly pick up the work for those items where you've specifically 
set up the down server.  We use the server group/load balancer name for email 
and flashboards as well as web services, etc. and it all works fine.

Anne Ramey
***********************************
E-mail correspondence to and from this address may be subject to the North 
Carolina Public Records Law and may be disclosed to third parties only by an 
authorized State Official.


-----Original Message-----
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Lyle Taylor
Sent: Thursday, March 19, 2009 1:04 PM
To: [email protected]
Subject: Re: Installing Secondary Server in Server Group

I'm not sure about the documentation, but I will share one thing that I 
learned.  While all of the servers will have a common alias that outside 
clients will use to connect to the server group (hopefully), you don't want the 
flashboards and e-mail services hitting the alias.  When you install those, you 
should point them to the specific AR server that you want them working with.  
So, for example, if your server group alias is Remedy, and it is comprised of 
the servers ServerA and ServerB, the e-mail engine installed on ServerA should 
be configured to point to ServerA and not Remedy.  Same for flashboards.

Lyle

-----Original Message-----
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of bruce sisk
Sent: Thursday, March 19, 2009 9:42 AM
To: [email protected]
Subject: Installing Secondary Server in Server Group

Good morning,

I am beginning to set up the second server that will then be configured in a 
server group.  The primary server is up and running as follows:

Windows 2003 Server
Oracle 10 DB (remote)
ARS 7.1 P6 - including email, approval, assignment, flashboards
CMDB 2.1 P4
AIE 7.1 P4
ITSM 7.0.3 P7
SLM 7.1 P1

I have successfully installed ARS 7.1 P6 (server only) on the secondary server 
using the shared DB option.  This is working as well.

My next steps are the various other components:  email, approval, etc.  Sadly, 
I have found very little in the way of instructions on this.  Some components 
have more than others...very inconsistent.

My question is...does BMC or somebody have a comprehensive white paper or 
instruction set that addresses installation of the other components like email.

Thanks,

Bruce Sisk
BFS Enterprises



________________________________________
PeoplePC Online
A better way to Internet
http://www.peoplepc.com

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


 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.



Portions of this message may be confidential under an exemption to Ohio's 
public records law or under a legal privilege. If you have received this 
message in error or due to an unauthorized transmission or interception, please 
delete all copies from your system without disclosing, copying, or transmitting 
this message.

Reply via email to