Re: [nv-l] IBM Tivoli Netview for Linux Installation
2005-07-29 09:32:35
Logical Volume Manage (LVM), its great
when you want to increase or add filesystems and in some cases delete filesystems
without having to change the partitions on the hard drive. I normally
create the following a /boot, a / root, a swap space, and then create
a LVM on the rest of the harddrive and then create the additional filesystem
within the LVM. like /usr/OV, /usr/OV/log, /usr/OV/www/log,
/opt, /playarea
Mark F Sklenarik IBM SWG Tivoli Solutions Quality
Assurance Business Impact Management and Event Correlation Software
Quality Engineer
"Rocco Scappatura"
<rocsca AT sttspa DOT it>
Sent by: owner-nv-l AT lists.us.ibm DOT com
07/29/2005 09:07 AM
|
To
| <nv-l AT lists.us.ibm DOT com>
|
cc
|
|
Subject
| Re: [nv-l] IBM Tivoli Netview
for Linux Installation |
|
Many thanks to you too..
Excuse me but I did not see you answer so I forward further insight
to
John...
At the moment, I never have used LVM. In what situation in suitable?
BR,
rocsca
----- Original Message -----
From: "Mark Sklenarik" <marksk AT us.ibm DOT com>
To: <nv-l AT lists.us.ibm DOT com>
Sent: Friday, July 29, 2005 2:49 PM
Subject: Re: [nv-l] IBM Tivoli Netview for Linux Installation
> Some additional ideas
> root "/" on SLES needs to be at least 3-4 GB,
> The reason being is if you plan to perform
online up dates, Yast2
> needs some place to copy the files to, until they are installed. I
have
> yet to determine where online update puts the temp install files,
I found
> this when an update failed and hung my machine, had to reinstall the
OS.
>
> Do not forget to create your swap space, with 4Gb of ram, normally
test
> makes a swap space 4 GB also
>
> I would also suggest after creating /, /boot, and swap space, you
use LVM
> functions of SLES 9, this will allow you to grow a file system if
you
> originally make it to small.
>
> /usr/OV - the Tivoli test organization normal sets this to about 4
GB,
> this allows room for the large trace files we sometime need to get.
>
> /opt - the Tivoli test organization normal sets this
to about 4 GB,
> since we end up install a number of other products on test systems.
>
> Mark F Sklenarik IBM SWG Tivoli Solutions Quality Assurance
Business
> Impact Management and Event Correlation Software Quality Engineer
>
>
>
>
> John M Gatrell <John.Gatrell AT uk.ibm DOT com>
> Sent by: owner-nv-l AT lists.us.ibm DOT com
> 07/29/2005 08:05 AM
> Please respond to
> nv-l
>
>
> To
> nv-l AT lists.us.ibm DOT com
> cc
>
> Subject
> Re: [nv-l] IBM Tivoli Netview for Linux Installation
>
>
>
>
>
>
>
> Just some hints, not to be taken as gospel (I am more familiar with
other
> flavours of linux).
> Chances are a Xeon system has hardware raid so you will just see 1
disk of
> 73.4GB
> Starting from the standard install scheme, then
>
> Reduce size of /home to very small (1GB)
>
> In case you ever put other products on such as IBM java, or Tivoli
gateway
> add a /opt partition.
> /opt should be at least 2GB.
>
> Keep the root partition '/' small.
> Have a separate /boot partition.
>
> Netview is best in it's own /usr/OV partition.
>
> Split the rest of the disk into 2 partitions called
> /usr and /usr/OV
> say 30% to /usr and 60% to /usr/OV
>
> John Gatrell, BA, AIX Cert Specialist, Cisco CCNA.
>
>
> I need to install IBM Tivoli Netview 7.1.4 on a server IBM xSeries
336:
>
> - 2 x Processor Xeon 3.2 GHz/800MHz 1MB L2 Cache EM64T
> - 2 x HD 73.4 GB
> - 4GB ECC DDR2 SDRAM RDIMM
>
> with OS SLES 9.
>
> I'ld like to figure out what is the best partition scheme to use for
my
> platform.
>
> Many Thanks,
>
> rocsca
>
|
|
|