Re: 3583 with San Data Gateway
Hmm, may be I was wrong, I will contact TSM device support team to get the latest status of LTO drive and library requirement on TSM V4 and V5. Tivoli Storage Management Function Verification Test , FVT Automation Project Lead Office:408-256-3312 Home:650-757-1661 Cell:415-218-7880 AIM:smartbluewong Dept Y0LA /Bldg 050-3 / Office 3A64 IBM SSG Division 46 Bill Boyer [EMAIL PROTECTED]@VM.MARIST.EDU on 04/24/2002 12:03:51 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: 3583 with San Data Gateway They show up a GEN_DRIVE where? The TSMSCSI devices screen on the MMC console? OR when you DEF DRIVE them to TSM? There was an issue with the TSMSCSI driver not recognizing the drives as LTO, but they define correctly to TSM. You can also issue 'SHOW LIBRARY' in an admin session to display the device capabilities and such. I use this to make sure that TSM is communicating with the drives/library. Maybe the TSM Device Driver in the 4.2.2.0 maintenance level has the 'fix'. We got a special release from developement back in January when I did a client install on W2K and LTO. Bill -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of John Sent: Wednesday, April 24, 2002 2:01 PM To: [EMAIL PROTECTED] Subject: Re: 3583 with San Data Gateway Thats correct Bill The drives show up as follows: GEN_DRIVE \\Tape0 GEN_DRIVE \\Tape1 I am going on site again tomorrow to try and make some sense of it. It still concerns me that the windows device manager says that the SDG is probably not working correctly. I am not sure whether I should just accept that as normal as someone suggested. Based on my findings tomorrow, I will post the symptoms is much more detail. Rgds John - Original Message - From: Bill Boyer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 24, 2002 6:35 PM Subject: Re: 3583 with San Data Gateway I believe you're wrong. the \\.\Tapex means it is using a native Windows device driver and not the TSM SCSI device driver. Which is what he stated in the original email. He's using the IBM LTO device drivers, which is what the Admin book recommends. The Library itself will be managed with the TSMSCSI driver, but the drives use the IBM LTO device driver and show up and \\.\Tapex. If you were using the TSMSCSI driver the drives would be MTx.x.x.x format. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Anthony Wong Sent: Wednesday, April 24, 2002 12:36 PM To: [EMAIL PROTECTED] Subject: Re: 3583 with San Data Gateway Console as \\.\TapeX where X is a number. \\.\TapeX is a generic device driver As mention before, using generic device driver is not supported with TSM server on NTx. Since testing all available generic device drivers is time consuming and testing teams are no way to test all up-to-date generic device drivers against TSM server on NTx. IF customers need to use generic drvice driver for any reasons (RSM),use Microsoft OS certified device driver from the latest service pack. If Microsoft does not provide device driver for the deivce, try download latest certified device driver form the vender website. TSM testing team never use generic device against TSM with the following exception: 1. Restore backupset from local attached tape driver/libraries or SDG attached tape drive/libraries For more information about RSM , http://www.tivoli.com/support/storage_mgr/devices/magstar.html#magscsi The following environments are not presently supported: Removable Storage Manager (RSM) - controlled libraries on Windows 2000 IBM Ultrium devices when library is controlled by RSM on Windows 2000 Again, not presently supported does not means it will not work. Tivoli Storage Management Function Verification Test , FVT Automation Project Lead Office:408-256-3312 Home:650-757-1661 Cell:415-218-7880 AIM:smartbluewong Dept Y0LA /Bldg 050-3 / Office 3A64 IBM SSG Division 46 James Thompson [EMAIL PROTECTED]@VM.MARIST.EDU on 04/24/2002 07:38:08 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: 3583 with San Data Gateway With the 3583 and TSM on Win2k, the drives use the IBM device driver located at ftp://ftp.software.ibm.com/storage/devdrvr/Win2000/ Once you've installed the driver and configured the drives to use this driver, you should be able to see the drives under the TSM Management Console as \\.\TapeX where X is a number. The library part can either be controlled by the Windows RSM or by the TSM device driver. James Thompson _ MSN Photos is the easiest way to share
Re: 3583 with San Data Gateway
TSM server patch 4.2.1.15 or 5.1.0.1 adsmscsi.sys START supporting LTO library and LTO drive. Install on NT should be easy and quick , However, on W2K , Customer need to disable Microsoft RSM take control over the LTO library and LTO drive or TSM server will not work correctly, I will keep posting as soon as I find more information or documents related to this issue. Tivoli Storage Management Function Verification Test , FVT Automation Project Lead Office:408-256-3312 Home:650-757-1661 Cell:415-218-7880 AIM:smartbluewong Dept Y0LA /Bldg 050-3 / Office 3A64 IBM SSG Division 46 John [EMAIL PROTECTED]@VM.MARIST.EDU on 04/24/2002 11:00:45 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: 3583 with San Data Gateway Thats correct Bill The drives show up as follows: GEN_DRIVE \\Tape0 GEN_DRIVE \\Tape1 I am going on site again tomorrow to try and make some sense of it. It still concerns me that the windows device manager says that the SDG is probably not working correctly. I am not sure whether I should just accept that as normal as someone suggested. Based on my findings tomorrow, I will post the symptoms is much more detail. Rgds John - Original Message - From: Bill Boyer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 24, 2002 6:35 PM Subject: Re: 3583 with San Data Gateway I believe you're wrong. the \\.\Tapex means it is using a native Windows device driver and not the TSM SCSI device driver. Which is what he stated in the original email. He's using the IBM LTO device drivers, which is what the Admin book recommends. The Library itself will be managed with the TSMSCSI driver, but the drives use the IBM LTO device driver and show up and \\.\Tapex. If you were using the TSMSCSI driver the drives would be MTx.x.x.x format. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Anthony Wong Sent: Wednesday, April 24, 2002 12:36 PM To: [EMAIL PROTECTED] Subject: Re: 3583 with San Data Gateway Console as \\.\TapeX where X is a number. \\.\TapeX is a generic device driver As mention before, using generic device driver is not supported with TSM server on NTx. Since testing all available generic device drivers is time consuming and testing teams are no way to test all up-to-date generic device drivers against TSM server on NTx. IF customers need to use generic drvice driver for any reasons (RSM),use Microsoft OS certified device driver from the latest service pack. If Microsoft does not provide device driver for the deivce, try download latest certified device driver form the vender website. TSM testing team never use generic device against TSM with the following exception: 1. Restore backupset from local attached tape driver/libraries or SDG attached tape drive/libraries For more information about RSM , http://www.tivoli.com/support/storage_mgr/devices/magstar.html#magscsi The following environments are not presently supported: Removable Storage Manager (RSM) - controlled libraries on Windows 2000 IBM Ultrium devices when library is controlled by RSM on Windows 2000 Again, not presently supported does not means it will not work. Tivoli Storage Management Function Verification Test , FVT Automation Project Lead Office:408-256-3312 Home:650-757-1661 Cell:415-218-7880 AIM:smartbluewong Dept Y0LA /Bldg 050-3 / Office 3A64 IBM SSG Division 46 James Thompson [EMAIL PROTECTED]@VM.MARIST.EDU on 04/24/2002 07:38:08 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: 3583 with San Data Gateway With the 3583 and TSM on Win2k, the drives use the IBM device driver located at ftp://ftp.software.ibm.com/storage/devdrvr/Win2000/ Once you've installed the driver and configured the drives to use this driver, you should be able to see the drives under the TSM Management Console as \\.\TapeX where X is a number. The library part can either be controlled by the Windows RSM or by the TSM device driver. James Thompson _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx
Re: 3583 with San Data Gateway
The issue with adsmscsi doesn't recognize the Non-IBM LTO drives as LTO on the management console has been fixed in 4.2.1.11. This problem doesn't apply to IBM LTO drives. Adsmscsi does not support the IBM LTO drives (3580) and therefore \\.\tapex you see is the correct device name. And the device type on the MMC would be GENERIC instead of LTO. However, for the library (3583) on Win2K, you have 2 driver options - adsmscsi or IBM driver. With the IBM driver, you should see \\.\changerx whereas with adsmscsi, you will see lbx.x.x.x. Which device driver are you using for the library? The element addresses for the drives depend on which driver controls the library. Hunny Kershaw Internet Address: [EMAIL PROTECTED] Tivoli Storage Manager - Device Driver Development Tel (408) 256-2828, T/L 276-2828 Quality Policy = Commit to Quality, Customer Satisfaction, Continual Improvement Bill Boyer bill.boyer@VERIZTo: [EMAIL PROTECTED] ON.NET cc: Sent by: ADSM: Subject: Re: 3583 with San Data Gateway Dist Stor Manager [EMAIL PROTECTED] .EDU 04/24/2002 12:03 PM Please respond to ADSM: Dist Stor Manager They show up a GEN_DRIVE where? The TSMSCSI devices screen on the MMC console? OR when you DEF DRIVE them ) to TSM? There was an issue with the TSMSCSI driver not recognizing the drives as LTO, but they define correctly to TSM. You can also issue 'SHOW LIBRARY' in an admin session to display the device capabilities and such. I use this to make sure that TSM is communicating with the drives/library. Maybe the TSM Device Driver in the 4.2.2.0 maintenance level has the 'fix'. We got a special release from developement back in January when I did a client install on W2K and LTO. Bill -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of John Sent: Wednesday, April 24, 2002 2:01 PM To: [EMAIL PROTECTED] Subject: Re: 3583 with San Data Gateway Thats correct Bill The drives show up as follows: GEN_DRIVE \\Tape0 GEN_DRIVE \\Tape1 I am going on site again tomorrow to try and make some sense of it. It still concerns me that the windows device manager says that the SDG is probably not working correctly. I am not sure whether I should just accept that as normal as someone suggested. Based on my findings tomorrow, I will post the symptoms is much more detail. Rgds John - Original Message - From: Bill Boyer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 24, 2002 6:35 PM Subject: Re: 3583 with San Data Gateway I believe you're wrong. the \\.\Tapex means it is using a native Windows device driver and not the TSM SCSI device driver. Which is what he stated in the original email. He's using the IBM LTO device drivers, which is what the Admin book recommends. The Library itself will be managed with the TSMSCSI driver, but the drives use the IBM LTO device driver and show up and \\.\Tapex. If you were using the TSMSCSI driver the drives would be MTx.x.x.x format. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Anthony Wong Sent: Wednesday, April 24, 2002 12:36 PM To: [EMAIL PROTECTED] Subject: Re: 3583 with San Data Gateway Console as \\.\TapeX where X is a number. \\.\TapeX is a generic device driver As mention before, using generic device driver is not supported with TSM server on NTx. Since testing all available generic device drivers is time consuming and testing teams are no way to test all up-to-date generic device drivers against TSM server on NTx. IF customers need to use generic drvice driver for any reasons (RSM),use Microsoft OS certified device driver from the latest service pack. If Microsoft does not provide device driver for the deivce, try download latest certified device driver form the vender website. TSM testing team never use generic device against TSM with the following exception: 1. Restore backupset from local attached tape driver/libraries or SDG attached tape drive/libraries For more information about RSM , http://www.tivoli.com/support/storage_mgr/devices/magstar.html#magscsi The following environments are not presently supported: Removable Storage Manager (RSM) - controlled libraries on Windows 2000 IBM Ultrium devices when library is controlled by RSM on Windows 2000 Again, not presently supported does not means it will not work. Tivoli Storage Management Function Verification Test , FVT Automation Project Lead Office:408-256-3312 Home:650-757-1661 Cell:415-218-7880 AIM:smartbluewong Dept Y0LA /Bldg 050-3 / Office 3A64 IBM SSG
Re: 3583 with San Data Gateway
With the 3583 and TSM on Win2k, the drives use the IBM device driver located at ftp://ftp.software.ibm.com/storage/devdrvr/Win2000/ Once you've installed the driver and configured the drives to use this driver, you should be able to see the drives under the TSM Management Console as \\.\TapeX where X is a number. The library part can either be controlled by the Windows RSM or by the TSM device driver. James Thompson _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx
Re: 3583 with San Data Gateway
Console as \\.\TapeX where X is a number. \\.\TapeX is a generic device driver As mention before, using generic device driver is not supported with TSM server on NTx. Since testing all available generic device drivers is time consuming and testing teams are no way to test all up-to-date generic device drivers against TSM server on NTx. IF customers need to use generic drvice driver for any reasons (RSM),use Microsoft OS certified device driver from the latest service pack. If Microsoft does not provide device driver for the deivce, try download latest certified device driver form the vender website. TSM testing team never use generic device against TSM with the following exception: 1. Restore backupset from local attached tape driver/libraries or SDG attached tape drive/libraries For more information about RSM , http://www.tivoli.com/support/storage_mgr/devices/magstar.html#magscsi The following environments are not presently supported: Removable Storage Manager (RSM) - controlled libraries on Windows 2000 IBM Ultrium devices when library is controlled by RSM on Windows 2000 Again, not presently supported does not means it will not work. Tivoli Storage Management Function Verification Test , FVT Automation Project Lead Office:408-256-3312 Home:650-757-1661 Cell:415-218-7880 AIM:smartbluewong Dept Y0LA /Bldg 050-3 / Office 3A64 IBM SSG Division 46 James Thompson [EMAIL PROTECTED]@VM.MARIST.EDU on 04/24/2002 07:38:08 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: 3583 with San Data Gateway With the 3583 and TSM on Win2k, the drives use the IBM device driver located at ftp://ftp.software.ibm.com/storage/devdrvr/Win2000/ Once you've installed the driver and configured the drives to use this driver, you should be able to see the drives under the TSM Management Console as \\.\TapeX where X is a number. The library part can either be controlled by the Windows RSM or by the TSM device driver. James Thompson _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx
Re: 3583 with San Data Gateway
I believe you're wrong. the \\.\Tapex means it is using a native Windows device driver and not the TSM SCSI device driver. Which is what he stated in the original email. He's using the IBM LTO device drivers, which is what the Admin book recommends. The Library itself will be managed with the TSMSCSI driver, but the drives use the IBM LTO device driver and show up and \\.\Tapex. If you were using the TSMSCSI driver the drives would be MTx.x.x.x format. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Anthony Wong Sent: Wednesday, April 24, 2002 12:36 PM To: [EMAIL PROTECTED] Subject: Re: 3583 with San Data Gateway Console as \\.\TapeX where X is a number. \\.\TapeX is a generic device driver As mention before, using generic device driver is not supported with TSM server on NTx. Since testing all available generic device drivers is time consuming and testing teams are no way to test all up-to-date generic device drivers against TSM server on NTx. IF customers need to use generic drvice driver for any reasons (RSM),use Microsoft OS certified device driver from the latest service pack. If Microsoft does not provide device driver for the deivce, try download latest certified device driver form the vender website. TSM testing team never use generic device against TSM with the following exception: 1. Restore backupset from local attached tape driver/libraries or SDG attached tape drive/libraries For more information about RSM , http://www.tivoli.com/support/storage_mgr/devices/magstar.html#magscsi The following environments are not presently supported: Removable Storage Manager (RSM) - controlled libraries on Windows 2000 IBM Ultrium devices when library is controlled by RSM on Windows 2000 Again, not presently supported does not means it will not work. Tivoli Storage Management Function Verification Test , FVT Automation Project Lead Office:408-256-3312 Home:650-757-1661 Cell:415-218-7880 AIM:smartbluewong Dept Y0LA /Bldg 050-3 / Office 3A64 IBM SSG Division 46 James Thompson [EMAIL PROTECTED]@VM.MARIST.EDU on 04/24/2002 07:38:08 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: 3583 with San Data Gateway With the 3583 and TSM on Win2k, the drives use the IBM device driver located at ftp://ftp.software.ibm.com/storage/devdrvr/Win2000/ Once you've installed the driver and configured the drives to use this driver, you should be able to see the drives under the TSM Management Console as \\.\TapeX where X is a number. The library part can either be controlled by the Windows RSM or by the TSM device driver. James Thompson _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx
Re: 3583 with San Data Gateway
Thats correct Bill The drives show up as follows: GEN_DRIVE \\Tape0 GEN_DRIVE \\Tape1 I am going on site again tomorrow to try and make some sense of it. It still concerns me that the windows device manager says that the SDG is probably not working correctly. I am not sure whether I should just accept that as normal as someone suggested. Based on my findings tomorrow, I will post the symptoms is much more detail. Rgds John - Original Message - From: Bill Boyer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 24, 2002 6:35 PM Subject: Re: 3583 with San Data Gateway I believe you're wrong. the \\.\Tapex means it is using a native Windows device driver and not the TSM SCSI device driver. Which is what he stated in the original email. He's using the IBM LTO device drivers, which is what the Admin book recommends. The Library itself will be managed with the TSMSCSI driver, but the drives use the IBM LTO device driver and show up and \\.\Tapex. If you were using the TSMSCSI driver the drives would be MTx.x.x.x format. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Anthony Wong Sent: Wednesday, April 24, 2002 12:36 PM To: [EMAIL PROTECTED] Subject: Re: 3583 with San Data Gateway Console as \\.\TapeX where X is a number. \\.\TapeX is a generic device driver As mention before, using generic device driver is not supported with TSM server on NTx. Since testing all available generic device drivers is time consuming and testing teams are no way to test all up-to-date generic device drivers against TSM server on NTx. IF customers need to use generic drvice driver for any reasons (RSM),use Microsoft OS certified device driver from the latest service pack. If Microsoft does not provide device driver for the deivce, try download latest certified device driver form the vender website. TSM testing team never use generic device against TSM with the following exception: 1. Restore backupset from local attached tape driver/libraries or SDG attached tape drive/libraries For more information about RSM , http://www.tivoli.com/support/storage_mgr/devices/magstar.html#magscsi The following environments are not presently supported: Removable Storage Manager (RSM) - controlled libraries on Windows 2000 IBM Ultrium devices when library is controlled by RSM on Windows 2000 Again, not presently supported does not means it will not work. Tivoli Storage Management Function Verification Test , FVT Automation Project Lead Office:408-256-3312 Home:650-757-1661 Cell:415-218-7880 AIM:smartbluewong Dept Y0LA /Bldg 050-3 / Office 3A64 IBM SSG Division 46 James Thompson [EMAIL PROTECTED]@VM.MARIST.EDU on 04/24/2002 07:38:08 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: 3583 with San Data Gateway With the 3583 and TSM on Win2k, the drives use the IBM device driver located at ftp://ftp.software.ibm.com/storage/devdrvr/Win2000/ Once you've installed the driver and configured the drives to use this driver, you should be able to see the drives under the TSM Management Console as \\.\TapeX where X is a number. The library part can either be controlled by the Windows RSM or by the TSM device driver. James Thompson _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx
Re: 3583 with San Data Gateway
John, As to your question about the SDG not working correctly...the response that said don't worry about it is correct. There is no windows driver for the SDG, nor is one needed. If it concerns you, you can disable lun 0 using the command disableCC 2 from the either the serial port or via telnet. This is described in the Redbook Using TSM in a SAN environment on page 59. The example describes the process for the SDG Router, but it's good for the SDG as well. -Lloyd On Wed, 24 Apr 2002 19:00:45 +0100 John [EMAIL PROTECTED] wrote: Thats correct Bill The drives show up as follows: GEN_DRIVE \\Tape0 GEN_DRIVE \\Tape1 I am going on site again tomorrow to try and make some sense of it. It still concerns me that the windows device manager says that the SDG is probably not working correctly. I am not sure whether I should just accept that as normal as someone suggested. Based on my findings tomorrow, I will post the symptoms is much more detail. Rgds John - Original Message - From: Bill Boyer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 24, 2002 6:35 PM Subject: Re: 3583 with San Data Gateway I believe you're wrong. the \\.\Tapex means it is using a native Windows device driver and not the TSM SCSI device driver. Which is what he stated in the original email. He's using the IBM LTO device drivers, which is what the Admin book recommends. The Library itself will be managed with the TSMSCSI driver, but the drives use the IBM LTO device driver and show up and \\.\Tapex. If you were using the TSMSCSI driver the drives would be MTx.x.x.x format. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Anthony Wong Sent: Wednesday, April 24, 2002 12:36 PM To: [EMAIL PROTECTED] Subject: Re: 3583 with San Data Gateway Console as \\.\TapeX where X is a number. \\.\TapeX is a generic device driver As mention before, using generic device driver is not supported with TSM server on NTx. Since testing all available generic device drivers is time consuming and testing teams are no way to test all up-to-date generic device drivers against TSM server on NTx. IF customers need to use generic drvice driver for any reasons (RSM),use Microsoft OS certified device driver from the latest service pack. If Microsoft does not provide device driver for the deivce, try download latest certified device driver form the vender website. TSM testing team never use generic device against TSM with the following exception: 1. Restore backupset from local attached tape driver/libraries or SDG attached tape drive/libraries For more information about RSM , http://www.tivoli.com/support/storage_mgr/devices/magstar.html#magscsi The following environments are not presently supported: Removable Storage Manager (RSM) - controlled libraries on Windows 2000 IBM Ultrium devices when library is controlled by RSM on Windows 2000 Again, not presently supported does not means it will not work. Tivoli Storage Management Function Verification Test , FVT Automation Project Lead Office:408-256-3312 Home:650-757-1661 Cell:415-218-7880 AIM:smartbluewong Dept Y0LA /Bldg 050-3 / Office 3A64 IBM SSG Division 46 James Thompson [EMAIL PROTECTED]@VM.MARIST.EDU on 04/24/2002 07:38:08 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: 3583 with San Data Gateway With the 3583 and TSM on Win2k, the drives use the IBM device driver located at ftp://ftp.software.ibm.com/storage/devdrvr/Win2000/ Once you've installed the driver and configured the drives to use this driver, you should be able to see the drives under the TSM Management Console as \\.\TapeX where X is a number. The library part can either be controlled by the Windows RSM or by the TSM device driver. James Thompson _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx -- - Lloyd Dieter- Senior Technology Consultant Synergy, Inc. http://www.synergyinc.cc [EMAIL PROTECTED] Main:716-389-1260fax:716-389-1267 -
Re: 3583 with San Data Gateway
They show up a GEN_DRIVE where? The TSMSCSI devices screen on the MMC console? OR when you DEF DRIVE them to TSM? There was an issue with the TSMSCSI driver not recognizing the drives as LTO, but they define correctly to TSM. You can also issue 'SHOW LIBRARY' in an admin session to display the device capabilities and such. I use this to make sure that TSM is communicating with the drives/library. Maybe the TSM Device Driver in the 4.2.2.0 maintenance level has the 'fix'. We got a special release from developement back in January when I did a client install on W2K and LTO. Bill -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of John Sent: Wednesday, April 24, 2002 2:01 PM To: [EMAIL PROTECTED] Subject: Re: 3583 with San Data Gateway Thats correct Bill The drives show up as follows: GEN_DRIVE \\Tape0 GEN_DRIVE \\Tape1 I am going on site again tomorrow to try and make some sense of it. It still concerns me that the windows device manager says that the SDG is probably not working correctly. I am not sure whether I should just accept that as normal as someone suggested. Based on my findings tomorrow, I will post the symptoms is much more detail. Rgds John - Original Message - From: Bill Boyer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 24, 2002 6:35 PM Subject: Re: 3583 with San Data Gateway I believe you're wrong. the \\.\Tapex means it is using a native Windows device driver and not the TSM SCSI device driver. Which is what he stated in the original email. He's using the IBM LTO device drivers, which is what the Admin book recommends. The Library itself will be managed with the TSMSCSI driver, but the drives use the IBM LTO device driver and show up and \\.\Tapex. If you were using the TSMSCSI driver the drives would be MTx.x.x.x format. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Anthony Wong Sent: Wednesday, April 24, 2002 12:36 PM To: [EMAIL PROTECTED] Subject: Re: 3583 with San Data Gateway Console as \\.\TapeX where X is a number. \\.\TapeX is a generic device driver As mention before, using generic device driver is not supported with TSM server on NTx. Since testing all available generic device drivers is time consuming and testing teams are no way to test all up-to-date generic device drivers against TSM server on NTx. IF customers need to use generic drvice driver for any reasons (RSM),use Microsoft OS certified device driver from the latest service pack. If Microsoft does not provide device driver for the deivce, try download latest certified device driver form the vender website. TSM testing team never use generic device against TSM with the following exception: 1. Restore backupset from local attached tape driver/libraries or SDG attached tape drive/libraries For more information about RSM , http://www.tivoli.com/support/storage_mgr/devices/magstar.html#magscsi The following environments are not presently supported: Removable Storage Manager (RSM) - controlled libraries on Windows 2000 IBM Ultrium devices when library is controlled by RSM on Windows 2000 Again, not presently supported does not means it will not work. Tivoli Storage Management Function Verification Test , FVT Automation Project Lead Office:408-256-3312 Home:650-757-1661 Cell:415-218-7880 AIM:smartbluewong Dept Y0LA /Bldg 050-3 / Office 3A64 IBM SSG Division 46 James Thompson [EMAIL PROTECTED]@VM.MARIST.EDU on 04/24/2002 07:38:08 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: 3583 with San Data Gateway With the 3583 and TSM on Win2k, the drives use the IBM device driver located at ftp://ftp.software.ibm.com/storage/devdrvr/Win2000/ Once you've installed the driver and configured the drives to use this driver, you should be able to see the drives under the TSM Management Console as \\.\TapeX where X is a number. The library part can either be controlled by the Windows RSM or by the TSM device driver. James Thompson _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx
Re: 3583 with San Data Gateway
I'm thinking you are not using the IBM LTO device drivers. Bill is correct: the drive syntax will be \\.\Tapex. Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs, CO 80949 [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com or www.storserver.com (719)531-5926 Fax: (240)539-7175 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of John Sent: Wednesday, April 24, 2002 11:01 AM To: [EMAIL PROTECTED] Subject: Re: 3583 with San Data Gateway Thats correct Bill The drives show up as follows: GEN_DRIVE \\Tape0 GEN_DRIVE \\Tape1 I am going on site again tomorrow to try and make some sense of it. It still concerns me that the windows device manager says that the SDG is probably not working correctly. I am not sure whether I should just accept that as normal as someone suggested. Based on my findings tomorrow, I will post the symptoms is much more detail. Rgds John - Original Message - From: Bill Boyer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 24, 2002 6:35 PM Subject: Re: 3583 with San Data Gateway I believe you're wrong. the \\.\Tapex means it is using a native Windows device driver and not the TSM SCSI device driver. Which is what he stated in the original email. He's using the IBM LTO device drivers, which is what the Admin book recommends. The Library itself will be managed with the TSMSCSI driver, but the drives use the IBM LTO device driver and show up and \\.\Tapex. If you were using the TSMSCSI driver the drives would be MTx.x.x.x format. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Anthony Wong Sent: Wednesday, April 24, 2002 12:36 PM To: [EMAIL PROTECTED] Subject: Re: 3583 with San Data Gateway Console as \\.\TapeX where X is a number. \\.\TapeX is a generic device driver As mention before, using generic device driver is not supported with TSM server on NTx. Since testing all available generic device drivers is time consuming and testing teams are no way to test all up-to-date generic device drivers against TSM server on NTx. IF customers need to use generic drvice driver for any reasons (RSM),use Microsoft OS certified device driver from the latest service pack. If Microsoft does not provide device driver for the deivce, try download latest certified device driver form the vender website. TSM testing team never use generic device against TSM with the following exception: 1. Restore backupset from local attached tape driver/libraries or SDG attached tape drive/libraries For more information about RSM , http://www.tivoli.com/support/storage_mgr/devices/magstar.html#magscsi The following environments are not presently supported: Removable Storage Manager (RSM) - controlled libraries on Windows 2000 IBM Ultrium devices when library is controlled by RSM on Windows 2000 Again, not presently supported does not means it will not work. Tivoli Storage Management Function Verification Test , FVT Automation Project Lead Office:408-256-3312 Home:650-757-1661 Cell:415-218-7880 AIM:smartbluewong Dept Y0LA /Bldg 050-3 / Office 3A64 IBM SSG Division 46 James Thompson [EMAIL PROTECTED]@VM.MARIST.EDU on 04/24/2002 07:38:08 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:Re: 3583 with San Data Gateway With the 3583 and TSM on Win2k, the drives use the IBM device driver located at ftp://ftp.software.ibm.com/storage/devdrvr/Win2000/ Once you've installed the driver and configured the drives to use this driver, you should be able to see the drives under the TSM Management Console as \\.\TapeX where X is a number. The library part can either be controlled by the Windows RSM or by the TSM device driver. James Thompson _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx
Re: 3583 with San Data Gateway
1. The windows device manager always shows an exclamation mark next to the SDG (Will not properly recognise it or configure it). This is normal as long as you can see SCSI device attached to that SDG . 2. When trying to configure the drives and library into TSM, it will not work using the Windows 2000 element addressing but rather the generic addressing. This subsequently causes checkin libvol to fail (I think!) 1. Need to use adsm device driver adsmscsi.sys , go to service and make sure adsm device driver started by system or before start dsmserver. ***TSM server do not support using generic device driver on SDG attached device or local attached device on NTx *** 2. Need to use ADSM server utility to get the elements addressing, go to device information to get the element addressing. again, unload all windows device drivers and ONLY load SCSI device drive for ALL devices(libraries) in San Data Gateway. never use generic device driver come with windows or device FOR TSM OPERATION UNLESS YOU ARE DOING RESTORE local BACKUPSET FROM SDG Thanks and hope it help!! ^_^ Tivoli Storage Management Function Verification Test , FVT Automation Project Lead Office:408-256-3312 Home:650-757-1661 Cell:415-218-7880 AIM:smartbluewong Dept Y0LA /Bldg 050-3 / Office 3A64 IBM SSG Division 46 John [EMAIL PROTECTED]@VM.MARIST.EDU on 04/23/2002 11:55:00 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Subject:3583 with San Data Gateway TSM'ers I need help I am trying to configure the above on an Xseries box running Win2K advanced server. All the correct drivers have been used and all the components are at the correct firmware levels. All devices in the solution are connected to a 2109 S16 The problems I have encountered are as follows: 1. The windows device manager always shows an exclamation mark next to the SDG (Will not properly recognise it or configure it). 2. When trying to configure the drives and library into TSM, it will not work using the Windows 2000 element addressing but rather the generic addressing. This subsequently causes checkin libvol to fail (I think!) If any of you guys have ever configured something akin to this environment you may be able to help me answer a couple of questions: 1. Based on the above, does anything immediately come to mind, from your experience? 2. With the tape drives in the 3583 being SCSI but the attachment being Fiber, must the TSM server see the drives as SCSI of fiber drives? I know this may all sound rather vague but its the best way I could try and explain it... Help will be much appreciated. Thanks John
