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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Tape to Tape Drive Correlation

Status
Not open for further replies.

csherwood

Technical User
Nov 26, 2002
2
CA
We have a Win2k Master server here running NBU4.5 FP3, with Solaris, HP/UX and Windows Media servers, and I am getting alot of error 52's trying to mount tapes.

I have cranked up logging to see if I can find this, but I am having troubles cross referencing the data.

What I am trying to do is figure out which tape drive a tape was loaded into given the time and job logged. Like I said I have cranked up the logging on all the standard logs to 5 (maximum).

Any help you guys can provide would be greatly appreciated.

Thanks!
 
Have you cleaned all your drives?

I would also recommend upgrading to NBU 4.5 FP6
 
Personally - I would stay away from FP6 - There are know issues and you may get more 52 errors. Have you verified all communications using bpclntcmd?
 
Yes. All communications are fine. The tape(s) in question will fail in one drive, but in a later job, work fine. I have 2 libraries with 6 drives each, so I am assuming it is working since it gets mounted in a different drive.
 
If it is only one drive failing - You may want to consider replacing that drive as this may be hardware related.
 
I use to get numerous #52 errorcodes and it drove me batty. I have SSO and a tape SAN. I eventually minimized the occurrences by upgrading microde and zoning the drives to isolate windows and UNIX from sharing the same drives. I now only seem to get the errors on window media servers.
And even then I am still able to eventually get a good backup during the backup window because I retry failed backups at a rate of 3 tries every 2 hours.
 
>Personally - I would stay away from FP6 - There are know >issues and you may get more 52 errors.

Can you go into more details please? We're being pushed towards FP6 here to allow SSO under Windows 2003.

Thanks - Tim
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top