|
exchange
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Unexpected server shutdownI have had a unexpected system shutdown twice now. When I take a look at
event viewer I see that both times the online defragmentation of priv1.edb started just before the system shutdown. Because of holiday in both cases the last backup also didn't take place. Now I think that it has something to do with the backup not taking place and the online defragmentation but I can't find any info on this. Can anybody help me out here? Greetings, Mark Peereboom Meijer Plaatbewerking You'll want to enable a full memory dump, and analyze the dump file
(!analyze in windbg) the next time it occurs. A server shutdown is probably a kernal mode error in a device driver. If you have ASR set, the server will reboot. In that it happens during online defrag, a period of high IO, I'd suspect: 1. resource exhaustion 2. a storage driver 3. a storage filter driver (AV, Quota, etc.) If it were resource exhaustion, you should see some events in the system log. Show quote "Mark Peereboom" <MarkPeereb***@discussions.microsoft.com> wrote in message news:0305B3AB-31F1-41E0-9F8F-C98744C9CE26@microsoft.com... >I have had a unexpected system shutdown twice now. When I take a look at > event viewer I see that both times the online defragmentation of priv1.edb > started just before the system shutdown. Because of holiday in both cases > the > last backup also didn't take place. Now I think that it has something to > do > with the backup not taking place and the online defragmentation but I > can't > find any info on this. > Can anybody help me out here? > > Greetings, > > Mark Peereboom > Meijer Plaatbewerking System log doesn't display anything right before the notification of the
unexpected system shutdown. And the problem also isn't the online defragmentation of the exchange database because this takes place every night. Only in combination with a backup that didn't take place the server reboots. Turn off asr and set for a full dump (or at least a kernal dump). Then you
can analyze the dump file and get your answer. Show quote "Mark Peereboom" <MarkPeereb***@discussions.microsoft.com> wrote in message news:6895A550-850C-4B48-8755-9AF081B1980D@microsoft.com... > System log doesn't display anything right before the notification of the > unexpected system shutdown. And the problem also isn't the online > defragmentation of the exchange database because this takes place every > night. Only in combination with a backup that didn't take place the server > reboots. The system was set to automically restart after system failure. I turned this
off now. However the system was set to make a kernel dump but there is no dump file to be found. Show quote "John Fullbright [MVP]" wrote: > Turn off asr and set for a full dump (or at least a kernal dump). Then you > can analyze the dump file and get your answer. > > > "Mark Peereboom" <MarkPeereb***@discussions.microsoft.com> wrote in message > news:6895A550-850C-4B48-8755-9AF081B1980D@microsoft.com... > > System log doesn't display anything right before the notification of the > > unexpected system shutdown. And the problem also isn't the online > > defragmentation of the exchange database because this takes place every > > night. Only in combination with a backup that didn't take place the server > > reboots. > > > The next time the problem occurs, insted of rebooting a memory.dmp file will
be written to C:\windows (assumes c: is the boot device). Show quote "Mark Peereboom" <MarkPeereb***@discussions.microsoft.com> wrote in message news:02865F8A-7A58-4F4A-8457-00D9347ACB3E@microsoft.com... > The system was set to automically restart after system failure. I turned > this > off now. However the system was set to make a kernel dump but there is no > dump file to be found. > > "John Fullbright [MVP]" wrote: > >> Turn off asr and set for a full dump (or at least a kernal dump). Then >> you >> can analyze the dump file and get your answer. >> >> >> "Mark Peereboom" <MarkPeereb***@discussions.microsoft.com> wrote in >> message >> news:6895A550-850C-4B48-8755-9AF081B1980D@microsoft.com... >> > System log doesn't display anything right before the notification of >> > the >> > unexpected system shutdown. And the problem also isn't the online >> > defragmentation of the exchange database because this takes place every >> > night. Only in combination with a backup that didn't take place the >> > server >> > reboots. >> >> >>  |
|||||||||||||||||||||||
Other interesting topics