Zlatko, The sessions have ended, but session 3 was a backup session over SAN, session 41 started as soon as session 3 was finished. It seems to me that TSM is seeing only one drive for some weird reason.
Regards, Rick -----Oorspronkelijk bericht----- Van: Zlatko Krastev [mailto:[EMAIL PROTECTED] Verzonden: 27 augustus 2003 9:23 Aan: [EMAIL PROTECTED] Onderwerp: Re: Waiting for media? Why? Are you sure it is not waiting for the media used by session 3? Also I've seen mounts postponed during audit library. What is/was 'q se 3 f=d', 'q se 41 f=d', 'q mo' & 'q pr'? Zlatko Krastev IT Consultant Rick Harderwijk <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 27.08.2003 09:18 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Waiting for media? Why? Hi, I just looked at this output on my TSM 4.2.1.12 (Windows) server: Output Q Sess Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name Number Method State Time Sent Recvd Type ------ ------ ------ ------ ------- ------- ----- -------- ------------------- 1 Tcp/Ip IdleW 6,7 M 8,8 K 2,5 K Serv- Windows Server_1 er NT 2 Tcp/Ip IdleW 6,7 M 8,8 K 2,5 K Serv- Windows Server_2 er NT 3 Tcp/Ip RecvW 0 S 15,3 K 115,0 G Node WinNT Server_1_W2K 7 Tcp/Ip Run 0 S 61,9 K 108 Admin WinNT Admin 41 Tcp/Ip MediaW 1,3 H 352 735 Node WinNT Server_3_W2K 43 Tcp/Ip IdleW 1,5 M 533 410 Node WinNT Server_1_W2K 49 Tcp/Ip Run 0 S 130 124 Admin WinNT Admin and I find session 41 a bit odd. Why is it waiting for media, when I have 2 LTO drives available in my 3583 library? Server_1 and Server_2 are SAN clients, Server_3 is a LAN client. This is my PATH config, and this has worked before: Source Name Source Type Destination Destination On-Line Name Type ----------- ----------- ----------- ----------- ------- Server_2 SERVER DRIVE0 DRIVE Yes Server_2 SERVER DRIVE1 DRIVE Yes Server_2 SERVER DRIVE2 DRIVE Yes Server_1 SERVER DRIVE0 DRIVE Yes Server_1 SERVER DRIVE1 DRIVE Yes Server_1 SERVER DRIVE2 DRIVE Yes Q DRIV: Library Name Drive Name Device Type On-Line ------------ ------------ ----------- ------------ 3583LIB DRIVE0 LTO Yes 3583LIB DRIVE1 LTO Yes 3583LIB DRIVE2 LTO Yes We have been experiencing some problems with TSM but after replacing a GBIC on the SAN switch all worked again. I had one issue with the audit library command: it never seemed to end (it ran for about 18 hours after which I cancelled the process, because session 3 ( a backup that restarted after the reboot that didn't start before because it didn't find any drives (the paths where not online, so I didn't think that was odd) was also (!) waiting for media - with drives available to mount a tape. Could the unfinished / hanging / aborted audit library cause the issue in this case? Or is something else going on? If you need any further info, don't hesitate to ask... Kind regards, Rick Harderwijk Systems Administrator Factotum Media BV Oosterengweg 44 1212 CN Hilversum P.O. Box 335 1200 AH Hilversum The Netherlands Tel: +31-35-6881166 Fax: +31-35-6881199 E: [EMAIL PROTECTED]
