Our database is remote - meaning most of the data is in the database on a remote server. Only the application (Discovery application and the files that it needs) are on the C drive (along with other applications). This is Management's argument - if most of the data is on the database - then why do we need more than 16G of HD space, and 4G of ram. Even though the data is in the database, my position is that you still need more than 16G of HD for the application, and the files that the application needs to write to.
-----Original Message----- From: Susan Palmer <[email protected]> To: [email protected] Sent: Wed, Feb 10, 2010 11:29 am Subject: Re: Server Crash ** I don't use Discovery but can you have the files directed to a different server, like the db server? Susan On Wed, Feb 10, 2010 at 10:13 AM, Joe D'Souza <[email protected]> wrote: ** I G of free space on something like even your laptop, and you would be sobbing.. Literally.. You got to have way way way more than that.. try something like at least 50 GB of free space on your HD for a start.. Off course it also depends on how much memory your machine uses and what it is configured to use as swap, but 1 GB free space? That is ridiculous to say the least.. Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]]on Behalf Of Kathy Morris Sent: Wednesday, February 10, 2010 11:03 AM To: [email protected] Subject: Re: Server Crash ** 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"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
