Additional ideas:

1.       Check to see if your network operations team  has inserted a firewall 
or other latency-creating mechanic between the server and the DB.

General database tips
To avoid a decline in the BMC Remedy AR System server performance, remember the 
following tips:


·         Do not use a firewall between the BMC Remedy AR System server and 
database tiers. This can impact performance significantly.
[…]


2.       Check to see if you are taking advantage of preload threads:

Faster server initialization
You can now configure the server to use multiple threads (known as “preload 
threads”) when loading the cache from the database. This option allows the 
server to make better use of system resources such as CPU and network 
bandwidth, and can greatly reduce the time required to load the cache at server 
initialization. This option can also be configured for use during run time. For 
information about using this option, see “Using preload threads” in the 
Configuration Guide.


-David J. Easter
Manager of Product Management, Remedy Platform
BMC Software, Inc.

The opinions, statements, and/or suggested courses of action expressed in this 
E-mail do not necessarily reflect those of BMC Software, Inc.  My voluntary 
participation in this forum is not intended to convey a role as a spokesperson, 
liaison or public relations representative for BMC Software, Inc.

From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Terje Moglestue
Sent: Thursday, March 01, 2012 8:56 AM
To: [email protected]
Subject: Re: Slow server starts

**
William,

I got the same issue on MS SQL on a remote server and find it very slow to 
start-up.

Are you using FQDN (fully qualified domain name) for all server references 
within BMC? With a correct setup in you DNS servers it should not make a 
difference. I found that we had less issues and quicker startup if I used FQDN 
for all server references.

Your RAM your your mid-tier sounds low to me. Bring it up to 4 CPU's and 
minimum 4 GB RAM. This make no difference in start up for the app server.
~
Terje

Sent from my iPad

On 1 Mar 2012, at 16:26, "William Abdo" 
<[email protected]<mailto:[email protected]>> wrote:
**
Hi All,
I am respectfully asking for your wisdom in an issue I am having.
I have noticed that our virtual servers are taking upwards to 45 minutes – 1 
hour to start-up.
This is unacceptable and I am currently in a guessing game for the true cause. 
Memory, connections, …
1 physical 124 gig running 6 virtual machines
4- 12 gig  ARS servers
2- 2 gig mid-tiers
All running Windows 2008
ARS 7.6.04 ITSM Suite
10 gig single nic
1 gig network pipeline

The Oracle database is on a different machine.
It used to take about 20 minutes to start and now it is upwards to 45 min to an 
hour.

Do you have any suggestions for this issue?


Respectfully,

William


This email message is intended for the use of the person to whom it has been 
sent, and may contain information that is confidential or legally protected. If 
you are not the intended recipient or have received this message in error, you 
are not authorized to copy, distribute, or otherwise use this message or its 
attachments. Please notify the sender immediately by return e-mail and 
permanently delete this message and any attachments. Verio, Inc. makes no 
warranty that this email is error or virus free. Thank you.
_attend WWRUG12 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers 
Are"_
_attend WWRUG12 www.wwrug.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"

Reply via email to