Re: Best Practices DISK for DB, LOG, and STGPOOL && JigSaw Puzzle
2006-09-19 09:53:57
Bernard
If you search for "partial page write" in the archives, there are many postings
covering the pros and cons of the log settings (ie H/W mirror, TSM mirror -
Parallel/Sequential)
The partial page write scenario is that to which Phillip was referring. As
always, there is a trade off between performance and protection.
The Admin Guide has a chapter on Protecting and Recovering your Server.
Take a look at the part that is called "Mirroring the Database and Recovery Log"
Leigh
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Bernaldo de Quiros, Iban 1
Sent: 19 September 2006 13:52
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Best Practices DISK for DB, LOG, and STGPOOL && JigSaw
Puzzle
Hi all,
Why to use TSM Mirror function for DB and RLOG if this can be supplied by
Hardware RAID ¿?
Using TSM mirror as far as I know could improve server performance...
But is it recommended to have the two phylosophies HW RAID and TSM mirror ¿? Or
only one of them...
Pro's/Con's or preferences for HW RAID or TSM mirror ¿?
Regards,
Iban Bernaldo De Quiros Y Marquez
Technical Specialist
Sun Microsystems, Inc.
Serrano Galvache, 56
Madrid 28033 ES
Phone +34 91 767 6233
Mobile + 34 659 01 91 12
Email Iban.Bernaldodequiros AT Sun DOT COM
-----Mensaje original-----
De: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] En nombre de
Richard Sims
Enviado el: jueves, 14 de septiembre de 2006 17:21
Para: ADSM-L AT VM.MARIST DOT EDU
Asunto: Re: [ADSM-L] Best Practices DISK for DB, LOG, and STGPOOL && JigSaw
Puzzle
On Sep 14, 2006, at 10:59 AM, Bernaldo de Quiros, Iban 1 wrote:
> Hi Richard,
>
> There's a lot of great stuff here and good advices !!
>
> But I have two last questions...
>
> 1-Will you share the same physical disk with database and storage pool
> ¿?
Never mix conflicting access-pattern subsystems in storage areas - that can be
as bad as tape and disk on the same I/O path. It is essential that your
database be as high-performance as possible, so keep it separate.
> 2-Will you spread database volumes over the same physical disk or over
> different physical disks ¿? Or will you make both ¿?
In a non-RAID environment, I would spread over physical disks, to the extent
reasonable. If very large disks, you may want a few partitions on the disk;
but then try to use 15,000 rpm disks. But I prefer using raw logical volumes
and hardware RAID 1+0 (striping and
mirroring) for best performance. And beyond that there are sophisticated disk
subsystems out there which offer further opportunities. Remember that TSM uses
one thread per disk volume, so you gain by having a reasonable number of
volumes.
Look back in the List archives for information posted from the hard- won
experiences of other contributors, as there's lots of good advice in our
collective efforts.
Richard Sims
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- Re: Best Practices DISK for DB, LOG, and STGPOOL && JigSaw Puzzle, Bernaldo de Quiros, Iban 1
- Re: Best Practices DISK for DB, LOG, and STGPOOL && JigSaw Puzzle, Bernaldo de Quiros, Iban 1
- Re: Best Practices DISK for DB, LOG, and STGPOOL && JigSaw Puzzle, Bernaldo de Quiros, Iban 1
- Re: Best Practices DISK for DB, LOG, and STGPOOL && JigSaw Puzzle, Bernaldo de Quiros, Iban 1
- Re: Best Practices DISK for DB, LOG, and STGPOOL && JigSaw Puzzle, Ford, Phillip
- Re: Best Practices DISK for DB, LOG, and STGPOOL && JigSaw Puzzle,
Leigh Reed <=
|
Previous by Date: |
Re: Best Practices DISK for DB, LOG, and STGPOOL && JigSaw Puzzle, Ford, Phillip |
Next by Date: |
AW: Migrate Inactive Files Feature Proposal, Salak Juraj |
Previous by Thread: |
Re: Best Practices DISK for DB, LOG, and STGPOOL && JigSaw Puzzle, Ford, Phillip |
Next by Thread: |
Logon failure after Registry restore., Nielsen, Bo |
Indexes: |
[Date]
[Thread]
[Top]
[All Lists] |
|
|