RE: SBS 2003 Premium - Midnight Crash
- From: Mastrom <Mastrom@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 7 Dec 2006 06:06:01 -0800
Hello Steve,
I didn't really solve the problem, just nutrealized it by turning off the
summarizing process in ISA. I hope that by deleting the logs that are
(probably) corrupted when I resume the process it will be able to complete
the summaries and ISA reports.
Unfortunately I didn't have time to spend on this so I still can't be
certain about how to end this problem for good.
Nikos
"Steve" wrote:
Nikos,.
I am experiencing a similar problem with midnight crashes but they appear to
be more intermittent (2-3 times a week). Have you had any luck in nailing
down the problem on your system? Any info will be appreciated.
Thanks,
Steve
"Mastrom" wrote:
I found what causes the crash. ISA creates logs which are summarized every
night at 12:30 to feed the weekly (or monthly etc) reports.
I found a few ISA reports not to be created so I asked to "create now" and
the server crashed with the usual error code (disk subsystem related).
So now I turned off the summarizing process until I solve the problem.
I will try to delete most of the logs just in case they are corrupted and
then activate it again. Anyway now I know what I'm fighting against and I
will do some research to deal with it. Any info will be appreciated.
I hope this helps others too.
Nikos
"Mastrom" wrote:
I did reschedule the maintenance of the exchange store (11-03) and it
finished normaly the online defragmentation around 11:30 withour a crash.
However my server did crash at 00:30 again with no obvious reason. So the
exchange failure was the result of the previous crash, not the cause of it.
Any ideas?
Nikos
"Mastrom" wrote:
Ok, I have more info to offer.
I've replaced the motherboard to make sure it's not the root of the
problems.
I'm not using the USB drive for Shadow Copies anymore.
I've also changed SATA cables for the system raid (C:).
After the change of motherboard I stayed at work monitoring the server until
the usual crashing time and it crashed again... :(
One process that I didn't realize it could be related was the maintenance
schedule of the exchange store. It starts at midnight and the online defrag
seems to take about half hour (according to logs). So it fits the
12:27-12:30 crash hour.
Until now I didn't have any problems with my exchange. The last crash of the
server took one of the two system disks off the raid and after replacing the
disk and doing some chkdsk repairs I let the server go back to work. The
raid rebuilds itself but exchange store database was damaged. Weird things
started to happen and I realize I have to take the store off-line.
I copy the exchange database files and logs to a safe place, I exmerge
everything to .pst files as a secondary backup, I create a recovery store,
restore the last backup of the store, swap the databases between the stores.
I checked again the restored database just in case it was corrupted in the
last backup and it seems ok. Now I'm making a new backup.
Could the midnight crash (BSO) happen from the scheduled maintenance of the
mailbox store? Anyone knows what exactly happens during that process? When
I have the oportunity (and learn more about this process) I will reschedule
it for a different time and see if the server crashes a different hour.
Any ideas or suggestions?
Nikos
- References:
- RE: SBS 2003 Premium - Midnight Crash
- From: Steve
- RE: SBS 2003 Premium - Midnight Crash
- Prev by Date: Re: Which anti-spam for SBS using pop3?
- Next by Date: Re: Moving to SMTP from POP3
- Previous by thread: RE: SBS 2003 Premium - Midnight Crash
- Next by thread: nic card loses address
- Index(es):
Relevant Pages
|
Loading
