Server crawls during backup

Hey there,

I have an SBS 2003 server that runs ridiculously slowly during the
backup process. So slowly in fact that the console is all but unusable.
It seems that the server freezes almost solid at times and then several
errors/warnings are logged immediately afterwards.

The server is new and the domain was swung using the Swing Kit and
Exchange Forklift. Other than the problems during the backup it runs
like a dream.

Specs:
Tyan Tiger K8SSA
Single AMD Operton Processor
4 GB Reg'd ECC Ram
3 x 150 GB WD 10K Raptor Disks - Raid 5 - Write Cache Disabled
Adaptec 2410SA

The backup drives are external 320 GB external USB hard drives. I have
used the same type on multiple servers without incident.

Event Viewer starting from 11pm when the backup begins, warnings/errors
only:

11pm - backup begins

Event Type: Warning
Event Source: ESE
Event Category: Performance
Event ID: 508
Date: 11/3/2006
Time: 11:30:03 PM
User: N/A
Computer: BUDDY
Description:
Information Store (5040) First Storage Group: A request to write to the
file "E:\EXData\E00.log" at offset 5169152 (0x00000000004ee000) for 512
(0x00000200) bytes succeeded, but took an abnormally long time (121
seconds) to be serviced by the OS. This problem is likely due to faulty
hardware. Please contact your hardware vendor for further assistance
diagnosing the problem.

For more information, click
http://www.microsoft.com/contentredirect.asp.


Event Type: Error
Event Source: MSExchangeIS Public Store
Event Category: Replication Errors
Event ID: 3079
Date: 11/3/2006
Time: 11:37:46 PM
User: N/A
Computer: BUDDY
Description:
Unexpected replication thread error 0x80004005 on database "First
Storage Group\Public Folder Store (BUDDY)".

FReplAgent


For more information, click
http://www.microsoft.com/contentredirect.asp.


Event Type: Warning
Event Source: ESENT
Event Category: Performance
Event ID: 508
Date: 11/3/2006
Time: 11:40:16 PM
User: N/A
Computer: BUDDY
Description:
ntfrs (2832) A request to write to the file
"c:\windows\ntfrs\jet\log\edb.log" at offset 5013504
(0x00000000004c8000) for 512 (0x00000200) bytes succeeded, but took an
abnormally long time (299 seconds) to be serviced by the OS. This
problem is likely due to faulty hardware. Please contact your hardware
vendor for further assistance diagnosing the problem.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1058
Date: 11/3/2006
Time: 11:42:32 PM
User: NT AUTHORITY\SYSTEM
Computer: BUDDY
Description:
Windows cannot access the file gpt.ini for GPO
CN={79ABAAD1-90E9-4760-8FC8-A26573C4EC3A},CN=Policies,CN=System,DC=horsejournals,DC=office.
The file must be present at the location
<\\horsejournals.office\SysVol\horsejournals.office\Policies\{79ABAAD1-90E9-4760-8FC8-A26573C4EC3A}\gpt.ini>.
(Configuration information could not be read from the domain
controller, either because the machine is unavailable, or access has
been denied. ). Group Policy processing aborted.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1030
Date: 11/3/2006
Time: 11:42:32 PM
User: NT AUTHORITY\SYSTEM
Computer: BUDDY
Description:
Windows cannot query for the list of Group Policy objects. Check the
event log for possible messages previously logged by the policy engine
that describes the reason for this.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Warning
Event Source: ESENT
Event Category: Performance
Event ID: 510
Date: 11/3/2006
Time: 11:50:09 PM
User: N/A
Computer: BUDDY
Description:
ntfrs (2832) A request to write to the file
"c:\windows\ntfrs\jet\log\edb.log" at offset 5046272
(0x00000000004d0000) for 512 (0x00000200) bytes succeeded, but took an
abnormally long time (256 seconds) to be serviced by the OS. In
addition, 0 other I/O requests to this file have also taken an
abnormally long time to be serviced since the last message regarding
this problem was posted 592 seconds ago. This problem is likely due to
faulty hardware. Please contact your hardware vendor for further
assistance diagnosing the problem.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Warning
Event Source: ESENT
Event Category: Performance
Event ID: 510
Date: 11/3/2006
Time: 11:53:41 PM
User: N/A
Computer: BUDDY
Description:
ntfrs (2832) A request to write to the file
"c:\windows\ntfrs\jet\log\edb.log" at offset 5062656
(0x00000000004d4000) for 512 (0x00000200) bytes succeeded, but took an
abnormally long time (158 seconds) to be serviced by the OS. In
addition, 0 other I/O requests to this file have also taken an
abnormally long time to be serviced since the last message regarding
this problem was posted 212 seconds ago. This problem is likely due to
faulty hardware. Please contact your hardware vendor for further
assistance diagnosing the problem.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Warning
Event Source: ESENT
Event Category: Performance
Event ID: 508
Date: 11/3/2006
Time: 11:55:00 PM
User: N/A
Computer: BUDDY
Description:
ntfrs (2832) A request to write to the file
"c:\windows\ntfrs\jet\sys\edb.chk" at offset 0 (0x0000000000000000) for
4096 (0x00001000) bytes succeeded, but took an abnormally long time (61
seconds) to be serviced by the OS. This problem is likely due to faulty
hardware. Please contact your hardware vendor for further assistance
diagnosing the problem.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


Event Type: Warning
Event Source: MSExchangeDSAccess
Event Category: LDAP
Event ID: 2392
Date: 11/3/2006
Time: 11:54:05 PM
User: N/A
Computer: BUDDY
Description:
Process WMIPRVSE.EXE -EMBEDDING (PID=5344). DSAccess failed to register
an Active Directory shutdown notification with the local server, error
0x55. To expedite the shutdown process, manually shut down Exchange
services before shutting down the server.

For more information, click
http://www.microsoft.com/contentredirect.asp.


Event Type: Warning
Event Source: ESE
Event Category: Performance
Event ID: 510
Date: 11/3/2006
Time: 11:57:51 PM
User: N/A
Computer: BUDDY
Description:
Information Store (5040) First Storage Group: A request to write to the
file "E:\EXData\E00.log" at offset 5234688 (0x00000000004fe000) for 512
(0x00000200) bytes succeeded, but took an abnormally long time (105
seconds) to be serviced by the OS. In addition, 0 other I/O requests to
this file have also taken an abnormally long time to be serviced since
the last message regarding this problem was posted 1667 seconds ago.
This problem is likely due to faulty hardware. Please contact your
hardware vendor for further assistance diagnosing the problem.

For more information, click
http://www.microsoft.com/contentredirect.asp.


Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2102
Date: 11/4/2006
Time: 12:01:27 AM
User: N/A
Computer: BUDDY
Description:
Process MAD.EXE (PID=3980). All Domain Controller Servers in use are
not responding:
buddy.horsejournals.office


For more information, click
http://www.microsoft.com/contentredirect.asp.


Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 1031
Date: 11/4/2006
Time: 12:03:07 AM
User: N/A
Computer: BUDDY
Description:
One of the System Attendant's task is blocked.
Function: CMonitoringTask::Work

For more information, click
http://www.microsoft.com/contentredirect.asp.


Various combinations of these errors continue on all night long usually
in clumps, which indicates that the server is hanging up for several
seconds and then coming back to life.

Any suggestions? Seems likely that this is hardware related, but is the
hardware most likely bad or misconfigured? Would a disabled write cache
cause this? How serious is it if left alone?

Thanks,

Pharismod

.

Relevant Pages

  • Re: What backup software do you use and why?
    ... Acronis does have hardware independent ... ongoing backup issues with a member server, ... I've used other than Arcserve and SBS Backup. ... One other thing - does Acronis have hardware-independent restore? ...
    (microsoft.public.windows.server.sbs)
  • RE: Moving SBS to new server as disaster recovery plan
    ... if you want to move the SBS system to another box with different ... hardware, you should not simply using backup/restore. ... Migrating from Small Business Server 2000 or Windows 2000 Server to Windows ... >I have a client that wants to use his old SBS box as a backup SBS server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Changing hardware issue
    ... server that we would like to have a backup of in case it goes down. ... We made an image of this server, and have gotten it to install before ... (on the original hardware). ... Virtualization would be nice... ...
    (alt.os.linux.redhat)
  • Re: Server crawls during backup
    ... It seems that the server freezes almost solid at times and then several ... Information Store First Storage Group: A request to write to the ... Please contact your hardware vendor for further assistance ... see Help and Support Center at ...
    (microsoft.public.windows.server.sbs)
  • Re: Options for a backup server (disaster purposes)
    ... Our backup is good, at least as of 1AM of that morning. ... As to the hardware, I mentioned in my post it is going to be a "base" ... server, just one that I can play with at home (practice, as you put it). ...
    (microsoft.public.windows.server.sbs)