Need advice on Exchange 2003 disc usage, Outlook clients timing out periodically

T

ted

I inherited a mail server, Dell 2950 with 8GB RAM and 2 Volumes.

C: = raid 1 70GB

D: = raid 5 1.5TB

The OS and OS swap file are on C:

Exchange 2003 and transaction logs are on the D: drive.

I ran the Exchange Troubleshooter:

Area: Disk Drive Health

Time Range: 07/07/2009 08:48:38 - 07/07/2009 08:53:32

Performance issue found on disk containing transaction log files.

Disk D:: Ratio of Reads/Writes = 1.29. Time Range: 07/07/2009

08:48:38 - 07/07/2009 08:53:32

The ratio of Reads I/Os to Writes I/Os on drive D: was 1.29. Generally,

this ratio should be less than 0.10; a higher ratio indicates that this disk

is used for something other than writing to the transaction log files. For

best performance, the log drive should be dedicated for transaction log

files.

Tell me more about this issue and how to resolve it.

Transaction log read latencies are high Time Range: 07/07/2009

08:48:38 - 07/07/2009 08:53:32

Transaction log disk: The average value for '\LogicalDisk(D:)\Avg. Disk

sec/Read' should be less than 0.005 (5 ms). The measured value is 0.005 (5

ms).

I also suspect diskpart was not run.

There's no room for more physical disks.

Ideas?

Thanks

- Ted
 
E

Ed Crowley [MVP]

How are the drives configured, i.e., RAID level and number of drives?

Ed Crowley MVP

"There are seldom good technological solutions to behavioral problems."

> .

"ted" <ted@ted.com> wrote in message

news:upnvpFcAKHA.4168@TK2MSFTNGP05.phx.gbl...
> I inherited a mail server, Dell 2950 with 8GB RAM and 2 Volumes.
> C: = raid 1 70GB
> D: = raid 5 1.5TB

> The OS and OS swap file are on C:
> Exchange 2003 and transaction logs are on the D: drive.

> I ran the Exchange Troubleshooter:

> Area: Disk Drive Health

> Time Range: 07/07/2009 08:48:38 - 07/07/2009 08:53:32

> Performance issue found on disk containing transaction log files.
> Disk D:: Ratio of Reads/Writes = 1.29. Time Range: 07/07/2009
> 08:48:38 - 07/07/2009 08:53:32
> The ratio of Reads I/Os to Writes I/Os on drive D: was 1.29.
> Generally, this ratio should be less than 0.10; a higher ratio indicates
> that this disk is used for something other than writing to the transaction
> log files. For best performance, the log drive should be dedicated for
> transaction log files.
> Tell me more about this issue and how to resolve it.

> Transaction log read latencies are high Time Range: 07/07/2009
> 08:48:38 - 07/07/2009 08:53:32
> Transaction log disk: The average value for '\LogicalDisk(D:)\Avg.
> Disk sec/Read' should be less than 0.005 (5 ms). The measured value is
> 0.005 (5 ms).

> I also suspect diskpart was not run.

> There's no room for more physical disks.

> Ideas?

> Thanks

> - Ted

>
 
E

Ed Crowley [MVP]

Also, how many users are hosted on this system?

Ed Crowley MVP

"There are seldom good technological solutions to behavioral problems."

> .

"ted" <ted@ted.com> wrote in message

news:upnvpFcAKHA.4168@TK2MSFTNGP05.phx.gbl...
> I inherited a mail server, Dell 2950 with 8GB RAM and 2 Volumes.
> C: = raid 1 70GB
> D: = raid 5 1.5TB

> The OS and OS swap file are on C:
> Exchange 2003 and transaction logs are on the D: drive.

> I ran the Exchange Troubleshooter:

> Area: Disk Drive Health

> Time Range: 07/07/2009 08:48:38 - 07/07/2009 08:53:32

> Performance issue found on disk containing transaction log files.
> Disk D:: Ratio of Reads/Writes = 1.29. Time Range: 07/07/2009
> 08:48:38 - 07/07/2009 08:53:32
> The ratio of Reads I/Os to Writes I/Os on drive D: was 1.29.
> Generally, this ratio should be less than 0.10; a higher ratio indicates
> that this disk is used for something other than writing to the transaction
> log files. For best performance, the log drive should be dedicated for
> transaction log files.
> Tell me more about this issue and how to resolve it.

> Transaction log read latencies are high Time Range: 07/07/2009
> 08:48:38 - 07/07/2009 08:53:32
> Transaction log disk: The average value for '\LogicalDisk(D:)\Avg.
> Disk sec/Read' should be less than 0.005 (5 ms). The measured value is
> 0.005 (5 ms).

> I also suspect diskpart was not run.

> There's no room for more physical disks.

> Ideas?

> Thanks

> - Ted

>
 
T

ted

C: = raid 1, 70GB, 2 drives

D: = raid 5, 1.5TB, 5 drives

80 users

- ted

"Ed Crowley [MVP]" <curspice@nospam.net> wrote in message

news:uFiJ65dAKHA.1336@TK2MSFTNGP05.phx.gbl...
> Also, how many users are hosted on this system?
> > Ed Crowley MVP
> "There are seldom good technological solutions to behavioral problems."
> .

> "ted" <ted@ted.com> wrote in message
> news:upnvpFcAKHA.4168@TK2MSFTNGP05.phx.gbl...
> >I inherited a mail server, Dell 2950 with 8GB RAM and 2 Volumes.
> > C: = raid 1 70GB
> > D: = raid 5 1.5TB
>

>> The OS and OS swap file are on C:
> > Exchange 2003 and transaction logs are on the D: drive.
>

>> I ran the Exchange Troubleshooter:
>

>> Area: Disk Drive Health
>

>> Time Range: 07/07/2009 08:48:38 - 07/07/2009 08:53:32
>

>> Performance issue found on disk containing transaction log files.
> > Disk D:: Ratio of Reads/Writes = 1.29. Time Range: 07/07/2009
> > 08:48:38 - 07/07/2009 08:53:32
> > The ratio of Reads I/Os to Writes I/Os on drive D: was 1.29.
> > Generally, this ratio should be less than 0.10; a higher ratio indicates
> > that this disk is used for something other than writing to the
> > transaction log files. For best performance, the log drive should be
> > dedicated for transaction log files.
> > Tell me more about this issue and how to resolve it.
>

>> Transaction log read latencies are high Time Range: 07/07/2009
> > 08:48:38 - 07/07/2009 08:53:32
> > Transaction log disk: The average value for '\LogicalDisk(D:)\Avg.
> > Disk sec/Read' should be less than 0.005 (5 ms). The measured value is
> > 0.005 (5 ms).
>

>
>> I also suspect diskpart was not run.
>

>> There's no room for more physical disks.
>

>> Ideas?
>

>> Thanks
>

>> - Ted
>

>>

>
 
E

Ed Crowley [MVP]

If you have enough space on your C: drive to hold a few days' log files,

then the easiest thing you could try is to move the log and system files to

C:. For performance and recoverability, it is a best practice to keep the

logs on a separate physical volume from the databases.

Ed Crowley MVP

"There are seldom good technological solutions to behavioral problems."

> .

"ted" <ted@ted.com> wrote in message

news:uACoxFxAKHA.4984@TK2MSFTNGP05.phx.gbl...
> C: = raid 1, 70GB, 2 drives
> D: = raid 5, 1.5TB, 5 drives

> 80 users

> - ted

> "Ed Crowley [MVP]" <curspice@nospam.net> wrote in message
> news:uFiJ65dAKHA.1336@TK2MSFTNGP05.phx.gbl...
> > Also, how many users are hosted on this system?
> > > > Ed Crowley MVP
> > "There are seldom good technological solutions to behavioral problems."
> > .
>

>> "ted" <ted@ted.com> wrote in message
> > news:upnvpFcAKHA.4168@TK2MSFTNGP05.phx.gbl...
> >>I inherited a mail server, Dell 2950 with 8GB RAM and 2 Volumes.
> >> C: = raid 1 70GB
> >> D: = raid 5 1.5TB
> >
>>> The OS and OS swap file are on C:
> >> Exchange 2003 and transaction logs are on the D: drive.
> >
>>> I ran the Exchange Troubleshooter:
> >
>>> Area: Disk Drive Health
> >
>>> Time Range: 07/07/2009 08:48:38 - 07/07/2009 08:53:32
> >
>>> Performance issue found on disk containing transaction log files.
> >> Disk D:: Ratio of Reads/Writes = 1.29. Time Range: 07/07/2009
> >> 08:48:38 - 07/07/2009 08:53:32
> >> The ratio of Reads I/Os to Writes I/Os on drive D: was 1.29.
> >> Generally, this ratio should be less than 0.10; a higher ratio indicates
> >> that this disk is used for something other than writing to the
> >> transaction log files. For best performance, the log drive should be
> >> dedicated for transaction log files.
> >> Tell me more about this issue and how to resolve it.
> >
>>> Transaction log read latencies are high Time Range: 07/07/2009
> >> 08:48:38 - 07/07/2009 08:53:32
> >> Transaction log disk: The average value for '\LogicalDisk(D:)\Avg.
> >> Disk sec/Read' should be less than 0.005 (5 ms). The measured value is
> >> 0.005 (5 ms).
> >
>>
>>> I also suspect diskpart was not run.
> >
>>> There's no room for more physical disks.
> >
>>> Ideas?
> >
>>> Thanks
> >
>>> - Ted
> >
>>>

> >


>
 
T

ted

OK. We will try that. We have 60GB free on C:, which should be enough for a

while.

Much appreciated.

"Ed Crowley [MVP]" <curspice@nospam.net> wrote in message

news:umfO%23d1AKHA.1376@TK2MSFTNGP02.phx.gbl...
> If you have enough space on your C: drive to hold a few days' log files,
> then the easiest thing you could try is to move the log and system files
> to C:. For performance and recoverability, it is a best practice to keep
> the logs on a separate physical volume from the databases.
> > Ed Crowley MVP
> "There are seldom good technological solutions to behavioral problems."
> .

> "ted" <ted@ted.com> wrote in message
> news:uACoxFxAKHA.4984@TK2MSFTNGP05.phx.gbl...
> > C: = raid 1, 70GB, 2 drives
> > D: = raid 5, 1.5TB, 5 drives
>

>> 80 users
>

>> - ted
>

>> "Ed Crowley [MVP]" <curspice@nospam.net> wrote in message
> > news:uFiJ65dAKHA.1336@TK2MSFTNGP05.phx.gbl...
> >> Also, how many users are hosted on this system?
> >> > >> Ed Crowley MVP
> >> "There are seldom good technological solutions to behavioral problems."
> >> .
> >
>>> "ted" <ted@ted.com> wrote in message
> >> news:upnvpFcAKHA.4168@TK2MSFTNGP05.phx.gbl...
> >>>I inherited a mail server, Dell 2950 with 8GB RAM and 2 Volumes.
> >>> C: = raid 1 70GB
> >>> D: = raid 5 1.5TB
> >>
>>>> The OS and OS swap file are on C:
> >>> Exchange 2003 and transaction logs are on the D: drive.
> >>
>>>> I ran the Exchange Troubleshooter:
> >>
>>>> Area: Disk Drive Health
> >>
>>>> Time Range: 07/07/2009 08:48:38 - 07/07/2009 08:53:32
> >>
>>>> Performance issue found on disk containing transaction log
> >>> files.
> >>> Disk D:: Ratio of Reads/Writes = 1.29. Time Range: 07/07/2009
> >>> 08:48:38 - 07/07/2009 08:53:32
> >>> The ratio of Reads I/Os to Writes I/Os on drive D: was 1.29.
> >>> Generally, this ratio should be less than 0.10; a higher ratio
> >>> indicates that this disk is used for something other than writing to
> >>> the transaction log files. For best performance, the log drive should
> >>> be dedicated for transaction log files.
> >>> Tell me more about this issue and how to resolve it.
> >>
>>>> Transaction log read latencies are high Time Range: 07/07/2009
> >>> 08:48:38 - 07/07/2009 08:53:32
> >>> Transaction log disk: The average value for '\LogicalDisk(D:)\Avg.
> >>> Disk sec/Read' should be less than 0.005 (5 ms). The measured value is
> >>> 0.005 (5 ms).
> >>
>>>
>>>> I also suspect diskpart was not run.
> >>
>>>> There's no room for more physical disks.
> >>
>>>> Ideas?
> >>
>>>> Thanks
> >>
>>>> - Ted
> >>
>>>
>>>

>

>>

>
 

Top