Unsolved
This post is more than 5 years old
3 Posts
0
15257
January 8th, 2003 13:00
Server rebbot during information store backup
Hi everyone,
Let me give you a quick rundown of our systems.
Veritas Backup Exec 8.6 Media Server:
PowerEdge 2550
Windows Advanced 2000 Server
Exchange 2000 Server:
PowerEdge 2550
Windows Advanced 2000 Server
During a backup of the information store, the mail server reboots itself. It gives no warning or anything. It looks as if someone had pushed the reset button. The only error reported is the "unexpected shutdown occured"!! lol Anybody have any input? This happens EVERYTIME I run a backup. I've seen others with reboot issues here so I thought this might be a place to try.
Thanks in advance,
Travis
No Events found!
tbully
3 Posts
0
January 8th, 2003 13:00
BTW:
I've disabled Norton thinking that was causing the problem. Now I am wondering if it's a Dell / Hardware issue.
jaxen112
2 Posts
0
March 17th, 2003 14:00
ldreyno
1 Message
0
March 17th, 2003 20:00
I am having similar problems.
PowerEdge 4600 with external PowerVault 221s(PERC 3/DC controller) with Raid5 array, PowerVault 110 LTO NTBACKUP software.
When backing up array system will crash. Most of the times system will alarm for a few minutes then blue screen
with various stop codes. Perc controller replaced, motherboard replaced, tape drive replaced, tower emm module replaced, SP3 loaded.
Server still crashing. The array was bulit with ArrayManager 3.1.3. Next step is to build a test array in the bios of controller.
tbully
3 Posts
0
March 18th, 2003 11:00
Since this posting, I think I have figured out what causes these crashes during an Information Store backup. You guys can see if this fits your situation. It seems to happen after I remove somebody from Active Directory (and flag that their exchange box get deleted). The box doesn't actually get deleted even if I manually start the management processes on the exchange boxes. Once the server crashes (i.e. the exchange services stop and restart), the box is no longer in the list. Backups will then run without a hitch until the next time I delete an account.
Looks like another Microsoft "feature"? Can anyone else confirm?
Travis
jaxen112
2 Posts
0
March 18th, 2003 13:00
mcdonsco
4 Posts
0
May 9th, 2003 22:00
Nice, I have been searching EVERYWHERE for a resolve to this exact problem...I think it may be a Dell thing not MS as the folks in the MS newsgroups have not mentioned seeing this same thing happen, same with the Veritas newsgroups.
We have a 2550 running Exchange 2000 Enterprise and It reboots randomly but i think it happens 95% of the time during a backup using Veritas 9.0 from a remote workstation. I say 95% of the time because i seem to recall it doing this before when a backup was not running (but maybe only once or twice).
Anyway, if anyone including Dell every finds a resolution for this, please let me know: mcdonsco@yahoo.com I'd appreciate it.
Last note on this, I've done memory swaps as well, the first swap seemed to work most of the time, but it still rebooted a couple times. I'm using the second half of the memory now and it's doing it almost every night so it appears to have something to do with the memory or the slots as one half of the memory worked most of the time (2 weeks between reboots) and the other half didn't work right at all (rebooted every night).
Thanks
mfarrar
7 Posts
0
November 24th, 2003 16:00
I have a PowerEdge 2650 running Win2k and Exchange2k, and Veritas BackupExec 9.0.
The server just shutdown during a backup of the Exchange Mailboxes. It did not reboot, it literally shut off!
Any help you could offer would be appreciated.
Thanks in advance.
MF
osssi
20 Posts
0
November 25th, 2003 13:00
Had exactly the same problem more than a year ago with PE2400 and standard Windows 2000 Server backup utility. I was suspecting antivirus system, MS Exchange Information Store process, etc. and was shutting them down one by one for backup time, but nothing helped actually. I was asking for help in this forum with no luck. During half a year I was taking a backup remotely using another server's backup system and accidentially realized that problem has gone... Probably some of MS updates made some change...
Alex