This is a good point and well put. I just need a strong argument to fight to
get this fixed. I am spending hours trying to recover the application because
-- ooops forgot to mention - they did not back up the config files on the
server so the Discovery file that got corrupted we are unable to restore. And
the developer who built the application did not keep a copy either. Unreal.
Trying to get them to understand that the Discovery server can not keep
history, and run the jobs on a 16G Hard Drive, and 4G of RAM, is obviously
challenging because I am not dealing with realist.
-----Original Message-----
From: Rick Cook <[email protected]>
To: [email protected]
Sent: Wed, Feb 10, 2010 11:11 am
Subject: Re: Server Crash
** Kathy, this is the information you need to take to management. Tell them
that 16GB is sufficient if they are content to only store ONE discovery run.
But since one of the features they paid for with the application was the
ability to track history, they are losing that value by restricting your
storage space for those discovery runs. So it's then up to them which has more
value - disk space or historical data. Get it in writing (email).
When they say "Disk space", and if they at some point want some of that
historical data, you can hold up your piece of paper documenting their decision.
Rick
On Wed, Feb 10, 2010 at 8:02 AM, Kathy Morris <[email protected]> wrote:
** After deleting temp files, I have 1G of HD space left. I can delete more
discovery files also, however aren't these files going to regenerate again when
I run a synchronization? I noticed files are continually created on our
application server by discovery. Our Management believes every application
server should be low disk space. They recently increased the hard drive space
to 16G (which they thought was a "favor"). I am trying to find out more info
about the Discovery allocation of space, so that I can explain WHY we need more
space to my Management. To me it's quite simple - 16G is ridiculous, but I
can't use that for an argument.
-----Original Message-----
From: Rick Cook <[email protected]>
To: [email protected]
Sent: Wed, Feb 10, 2010 10:53 am
Subject: Re: Server Crash
Seriously, upon what are Management's beliefs based? This seems like an
arbitrary limitation. That being said, there are probably some old discovery
files you could delete to free up some space.
Maybe ask them how much history they want you to store. That way, they can
choose between some cheap disk space and what may be more valuable data. And
since their decision will have been an informed one, they are responsible for
it.
Rick
From: Kathy Morris <[email protected]>
Date: Wed, 10 Feb 2010 10:37:19 -0500
To: <[email protected]>
Subject: Server Crash
**
Hi All,
We have 16G on our Application Server. Our Application Server runs Discovery
1.6.
Our database is remote. We have right now 1G of space left.
Our Management believes there is no reason why 16G is not sufficient space for
this Discovery application to run parallel with other applications.
We have other applications running on this server like HP Openview, SQL Server,
VMware, etc...
I noticed when Discovery runs (during synchronization) files are created also
on the application server (i.e. java files, tmp files, etc..). And if logging
is on, then files are created also.
Is 16G an reasonable size to run Discovery 1.6?
_Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_
_Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_
_Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
