On 4/27/07, thad <[EMAIL PROTECTED]> wrote:
>
> if this is going to host prod DBs and you'll be running them in
> archive log mode, you need to consider how you'll distribute the I/O
> on your disks. we have the archive logs and DBs on the same set of
> disks before and had some I/O issues during RMAN backup runs.
> and for the swap size, we tried to minimize swapping as much as we can.
Yes this will be used for production and will be housed in internal
disks. What raid type you recommend 0+1 or raid 5 for better
our SAN server is an EMC clariion cx700 so i believe its running on
RAID 5 by default. (correct me if i'm wrong). performance - it was
purchased before with a different environment in mind. it was ok when
the setup at work was not as big as we have today. and i think that
model is for SMEs so it really doesn't fit our requirement right now.
performance? BTW are you using kickstart server with standard image
LVM and package configs are are all from standard kickstart files
(some differences with HBA configuration). we have a mixture of HP and
IBM blades.
for Oracle in blade deployment? On other *nix with regards to RMAN we
usually schedule this when the system is not at its busiest hours to
our problem is the DBs are busy 24x5. weekend backups are ok. weekdays
- our DBA wants full backup made via RMAN for quick restoration (as he
reasoned out). we are rearranging this one using standby DBs (and will
probably put RMAN backups in the background for DR strategy).
avoid this problem and we zoned a separate hba for this purpose.
>
> here's the LVM layout that we use in our kickstart files for oracle db
servers:
>
> #part /boot --fstype ext3 --size=100 --ondisk=cciss/c0d0
> #part pv.100000 --size=100 --grow --ondisk=cciss/c0d0
> #volgroup vg00 --pesize=32768 pv.100000
> #logvol /var --fstype ext3 --name=lvsys03 --vgname=vg00 --size=512
> #logvol /opt --fstype ext3 --name=lvsys04 --vgname=vg00 --size=512
> #logvol /tmp --fstype ext3 --name=lvsys05 --vgname=vg00 --size=1536
> #logvol /home --fstype ext3 --name=lvsys06 --vgname=vg00 --size=256
> #logvol /local --fstype ext3 --name=lvdata01 --vgname=vg00 --size=1024
> #logvol /usr --fstype ext3 --name=lvsys02 --vgname=vg00 --size=2048
> #logvol / --fstype ext3 --name=lvsys00 --vgname=vg00 --size=256
> #logvol swap --fstype swap --name=lvsys01 --vgname=vg00 --size=8192
This is a nice minimalist / set-up, do you have X in this setup? What
are the important packages you usually include with this set-up?
we have X packages installed but X is not actually running. vncserver
is used during patch application and some occasional tasks requiring a
GUI.
i don't have the ks files online but i'll send you a PM for the list
of packages.
> these are all in the internal disks (with internal raid) of our blade
machines.
> the FS for our DBs (and oracle itself) are hosted on SAN disks with
> the LVs created with
> at least 4 stripes.
I would really like to hosts the other filesystem in the SAN because
its more flexible to carved out luns for filesystems. We are also
booting on SAN but not yet on RHEL.
yes. flexibility and for DR - we can just move the set of LUNs from
the old machine to a new one.
thanks,
erik
--
roderick e. tapang, nclp
retapang at gmail dot com
(o_.' http://counter.li.org/
//\ ----------------------
V_/_ Linux User # 253842
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph
