schiffer4
asked on
Netware 6.5 SP7 freezes during backup by BE 2010 of specific volume
I have an HP ML350 G4 with 4 GB RAM and 2 xeon processors, hyperthreading turned off at the BIOS. I have been running BE backups to a network attached Overland storage server for over two years.
Lately I can back up the SYS and one other volume on the server no problem, but every time I try to backup the other volume on the server, the server freezes and the keyboard is unresponsive. Manual reboot is the only option, and there's no abend entry to look at to see where the problem is. I've done a NSS pool rebuild successfully on the mysterious volume, and I've run TSAFS on it from the server itself with no trouble. I've even set up individual backups to run one after the other, still with no success.
The server runs otherwise without any troubles.
Lately I can back up the SYS and one other volume on the server no problem, but every time I try to backup the other volume on the server, the server freezes and the keyboard is unresponsive. Manual reboot is the only option, and there's no abend entry to look at to see where the problem is. I've done a NSS pool rebuild successfully on the mysterious volume, and I've run TSAFS on it from the server itself with no trouble. I've even set up individual backups to run one after the other, still with no success.
The server runs otherwise without any troubles.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Jog log details: I only have Backup Exec version 9.2 installed here, cannot vouch for newer versions;
On the administration console (on the server) goto Jobs - Policy - Select the policy in use by the backup job, select Job log;
I can imagine that if there is some disk corruption under a file that isn't used by your users it would only show during a backup of all files. Maybe if you do a virusscan of all files you would experience the same trouble...
On the administration console (on the server) goto Jobs - Policy - Select the policy in use by the backup job, select Job log;
I can imagine that if there is some disk corruption under a file that isn't used by your users it would only show during a backup of all files. Maybe if you do a virusscan of all files you would experience the same trouble...
ASKER
Thank you, found the job log prefs under Tools-Options.
Another question I have is that I successfully backed up all of the volumes two nights in a row last week, and then on Friday it failed again. My concern is that I could be on a goose chase trying to figure our which hardware might be failing and have it turn out to be an NLM with a memory leak or, as you said before, a corrupted file.
Another question I have is that I successfully backed up all of the volumes two nights in a row last week, and then on Friday it failed again. My concern is that I could be on a goose chase trying to figure our which hardware might be failing and have it turn out to be an NLM with a memory leak or, as you said before, a corrupted file.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I just had the system status led go amber on the front, and upon looking inside I have two amber lights, one each on two RAM slots, so I'm assuming at this point that that would be my hardware failure. I'm going to try and install two new RAM sets and see if that makes a difference. Running low on RAM would definitely be an issue that would cause this, I'm sure.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I agree with deroode. Given the symptoms you describe, the intermittent nature and the fact the problem materialized out of the blue, hardware is a likely culprit. He's giving you good advice.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
ASKER
If it's a hardware problem that only occurs during the backups, do you have any idea where to start? Why would the server run happily every other time, including the backup of the other two volumes, and not during the backup of the third volume?