Author: "Schneider, John" <schnjd AT STLO.MERCY DOT NET>
Date: Thu, 10 May 2007 15:05:12 -0500
Greetings, We just installed a new TS3310 tape library on a Windows 2003 server running TSM 5.3.4.0. We configured library with all devices and slots in one partition. The library and drive drivers i
Check dsmserv.opt to verify: VOLUMEHistory /tsm/server/vol.history and then use "backup volhist" command. Try checking out a volume. Greetings, We just installed a new TS3310 tape library on a Window
Author: "Schneider, John" <schnjd AT STLO.MERCY DOT NET>
Date: Thu, 10 May 2007 19:17:36 -0500
Forgive me if I am being dense, but I don't see what your suggestion has to do with my problem. A Backup Volhist just copies the current volume history off to a disk file, it doesn't have anything to
Author: Igor Yakovenko <Igor_Yakovenko AT RU.IBM DOT COM>
Date: Fri, 11 May 2007 10:30:53 +0400
John, good day, could you print here information about paths from TSM to your library and drives (q path ... f=d)? Best regards, Igor Yakovenko "Schneider, John" <schnjd AT STLO DOT MERC Y.NET> To Se
Author: "Schneider, John" <schnjd AT STLO.MERCY DOT NET>
Date: Fri, 11 May 2007 08:38:17 -0500
Igor, Yes. Here it is. Do you have something in mind? Source Name: ROGE-TSM1 Source Type: SERVER Destination Name: IBM3576 Destination Type: LIBRARY Library: Node Name: Device: \\.\Changer1 External
When you audit the library try checklabel=barcode. Greetings, We just installed a new TS3310 tape library on a Windows 2003 server running TSM 5.3.4.0. We configured library with all devices and slot
Author: Igor Yakovenko <Igor_Yakovenko AT RU.IBM DOT COM>
Date: Fri, 11 May 2007 18:46:57 +0400
John, I had the situation (actually do not remember which) when I changed device name from \\.\ChangerN to lbX.X.X.X (for drives - the same) - it solved all of my problems. I mean in this case IBM li
Author: "Schneider, John" <schnjd AT STLO.MERCY DOT NET>
Date: Fri, 11 May 2007 10:47:09 -0500
Laura, Yes, that is how I do the Audit Library. Without checkl=barcode the audit would take a long time. And it runs successfully. Best Regards, John D. Schneider Sr. System Administrator - Storage S
John, Just suggestions. Sometimes the simplest answer is actually the solution. IBM also lists your error under Windows 2000 with it being a corrupt device driver. Best of luck, Laura --Original Mess
Author: "Schneider, John" <schnjd AT STLO.MERCY DOT NET>
Date: Fri, 11 May 2007 11:21:33 -0500
The problem has been resolved, thanks to TSM support. They had me look in the Windows event log (I can't believe I never looked there) and we found occasional errors coming out of Removable Storage M
Issue ts3310 related there should be configuration on the library console to assign io slots for library partition.I remember that configuration can not be done via web gui . Greetings, We just insta