We have an HP Netserver tc2110 running SCO Openserver 5.0.6 that is having trouble with backups with Lone-Tar. When the machine reaches the point where it verifies the data it just backed up, it reboots somewhere during the process. The tape drive is an HP VS 80 DLT drive. We have five other machines with the same configuration that are not experiencing this problem. Al of the settings for Lone-Tar appear to be correct and we can do Tar and CPIO backup and read operations without problem. Does anyone have any suggestions? Thanks.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
SCO 5.0.6 Server reboots during verify with Lone-Tar
- Thread starter tep0583
- Start date
Sounds like a hardware or at least firmware problem.
Does the problem occur when you do short jobs or only when you do a full system backup?
What do you mean by "same configuration"? Do you mean that the other machines have the same motherboard, same controller, and same tape drive? You should swap components between the machines and see if you can isolate whether the problem is the tape drive, controller, motherboard, or os/software settings.
Does the problem occur when you do short jobs or only when you do a full system backup?
What do you mean by "same configuration"? Do you mean that the other machines have the same motherboard, same controller, and same tape drive? You should swap components between the machines and see if you can isolate whether the problem is the tape drive, controller, motherboard, or os/software settings.
- Thread starter
- #3
I was leaning toward hardware myself, but I'm not sure if I should start with the drive or the controller. The problem only occurs during verification after a full system backup.
All of the machines are identical, all HP Netserver tc2110s with the same controller, DLT, OS (SCO 5.0.6), and backup software (Lone-Tar). The OS settings should also be identical, but I can check this. I would love to be able to swap componates between machines, but they are all remote units, with the problem machine being 4 hours away. None of the others can be taken out of service to swap parts with this unit. Seeing that we had some trouble making the tape drive work last week, I'm thinking that may be the problem.
I'll have to see if I can get HP to go out to look at the drive.
Thanks for the reply.
All of the machines are identical, all HP Netserver tc2110s with the same controller, DLT, OS (SCO 5.0.6), and backup software (Lone-Tar). The OS settings should also be identical, but I can check this. I would love to be able to swap componates between machines, but they are all remote units, with the problem machine being 4 hours away. None of the others can be taken out of service to swap parts with this unit. Seeing that we had some trouble making the tape drive work last week, I'm thinking that may be the problem.
I'll have to see if I can get HP to go out to look at the drive.
Thanks for the reply.
Since the problem is actually causing a system reboot, I would tend to think it is more likely to be controller or motherboard related than drive related. It is possible, but uncommon for a tape drive problem to cause the system to physically reset. Hard resets typically result from shorts to the motherboard itself, and a tape drive is pretty far removed from being able to short out the motherboard.
On the other hand, if the problem only occurs when you do a full backup vs a short partial backup, the problem may indeed be tape drive related.
Your guess is as good as mine regarding which component is bad.
On the other hand, if the problem only occurs when you do a full backup vs a short partial backup, the problem may indeed be tape drive related.
Your guess is as good as mine regarding which component is bad.
- Thread starter
- #5
- Status