Serve-You
asked on
Server hangs 3 a 4 minutes after starting a NTbackup sheduled task, when viewing The local disk, theres no disk space left.
When starting sheduled task on a windows 2003 SBS server, backuping data and exchange, 3 a 4 minutes after the backup has started the server hangs, In the event log application section1030 and 1058 messages are displayed. in the event system log event ID 2020 is logged . What schould be wrong. The problem doesn't occur when scheduled task in NTbackup are disabled, So i'm pretty sure that the problem is triggered by NTbackup. There are no removables devices in you Proliant server, we are backing up to a NAS (Thecus).
hans.txt
hans.txt
ASKER
We have looked at article 842804. It dindn't solve the problem.
We are working with service pack 2.
The problem doesn' t occur always but in 80 % it does. Strange thing is when viewing the NTbackup reports sometimes the problem occurs also. The server freezes completely and a restart is neccassary.
I have 2 server that have the same problem by 2 different clients. By One i Have stopt scheduled NTbackup and since then the problem doesn't occur, (but there is no backup, and that is not adviseabaly).
The servers are installed 3 week ago and all updates are installed.
When Running the backup manually the problem has not yet occured.
We are working with service pack 2.
The problem doesn' t occur always but in 80 % it does. Strange thing is when viewing the NTbackup reports sometimes the problem occurs also. The server freezes completely and a restart is neccassary.
I have 2 server that have the same problem by 2 different clients. By One i Have stopt scheduled NTbackup and since then the problem doesn't occur, (but there is no backup, and that is not adviseabaly).
The servers are installed 3 week ago and all updates are installed.
When Running the backup manually the problem has not yet occured.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Problem solved by making the backup completely by scripting.
Do you get this problem when you run the backups manually aswell, or only scheduled? What service pack is the server running at the moment?