We have a Dell PowerEdge 2600 (dedicated file server) and we use BE v10.1d on production level. BE v11d is still in test environment and won't be released to production until all bugs have been fixed.
We are also experiencing the same problem with our file server. As soon as the backup job hits that file server, the file server gets the blue screen...
"
Call your hardware vendor for support. NMI ? Parity Check / Memory parity Error
*** The system has halted ***
"
At first, we thought it was hardware issue. We've contacted Dell to troubleshoot this. We've been troubleshooting this for almost a year on this.
The Event Log does not show anything except the time gap and saying that the system had shutdown unexpectantly. The Dell OpenManage log just shows PCI Error.
We've ran all sorts of tools and tests. All says the hardware is fine. We even ran with Microsoft's Windows Memory Diagnostic Tool. That came clean as well.
We had the motherboard replaced. Still the same problem. We had the RAMs replaced recently....still monitoring.
After seeing this thread in the forum, I realize that the server hangs/crash does coincide at the moment when the backup job hits the file server.
Yes, we do use AOFO on the file server because it makes sense to use AOFO for backup on a file shared server. Yes, we've disabled and enabled the AOFO and still does not make a difference. Server still hangs/crash...
HOWEVER, I've noticed something different about this whole scenario. I've placed the file server at the top of the resource order, making it FIRST to backup...so far, it has not crashed YET.
When the file server is either, second on the list or middle of the list or last on the list, somehow, going from one resource to another causes the file server to crash. But putting the file server at the top of the resource, it has not crashed--YET.
I am still keeping a hawk eye on it. For the past few months, I've been sacrificing my family time on the weekend monitoring the backup job just to make sure the file server does not crash. When it does, all hell rains down and I have to go in just to push a button.
In summary, one thing is certain, this file server crash coincides when the backup job hits the file server if it is not First on the resource order. So it's not just a fluke or anamoly. I can be absolutely positive that the problem is related to Backup Exec and not hardware.