<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Connecting MSL5030 to windows 2000 in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/connecting-msl5030-to-windows-2000/m-p/3233198#M6027</link>
    <description>I did not mention above. The NSR N1200 was a second hand unit that came out of a working site. The unit should be fully functional but I can not guarantee that 100%</description>
    <pubDate>Mon, 29 Mar 2004 19:48:26 GMT</pubDate>
    <dc:creator>Lloyd_10</dc:creator>
    <dc:date>2004-03-29T19:48:26Z</dc:date>
    <item>
      <title>Connecting MSL5030 to windows 2000</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/connecting-msl5030-to-windows-2000/m-p/3233197#M6026</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I have recently purchased a MSL5030 Ultrium tape library to upgrade our backup solution. I purchased a NSR N1200 with the intention of connecting the MSL5030 to a SAN Storageworks fibre switch (8-EL) via the NSR. The old SAN configuration has 3 windows 2000 servers, a MDR and a HSG80 disk array plugged in to a SAN Storageworks fibre switch (8-EL). There is a HVD TL891 tape library connected to the SAN via the MDR that was used to perform the current/old backup jobs. This left 2 free spare ports on the SAN fibre switch which I connected a new windows 2000 backup server and the NSR with the MSL5030 attached. Once the new devices are attached all of the servers in the SAN can see the old tape drive, the NSR and the 2 Ultrium (LTO) tape drives but not the MSL Library in computer management/removable storage. We are currently using Arcserve 2000 to perform our backups, in Arcserve's device manager I can see the old tape drive and the NSR but nothing else. Also the old drive can not be used to perform backup jobs with the new devices attached, when you try a simple "hardware error" is the only error message.&lt;BR /&gt;&lt;BR /&gt;I have checked to ensure all the SCSI ID's are different. I do not know what else to check.&lt;BR /&gt;&lt;BR /&gt;does anyone have any suggestions?&lt;BR /&gt;Thanks,&lt;BR /&gt;Lloyd</description>
      <pubDate>Mon, 29 Mar 2004 19:45:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/connecting-msl5030-to-windows-2000/m-p/3233197#M6026</guid>
      <dc:creator>Lloyd_10</dc:creator>
      <dc:date>2004-03-29T19:45:44Z</dc:date>
    </item>
    <item>
      <title>Re: Connecting MSL5030 to windows 2000</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/connecting-msl5030-to-windows-2000/m-p/3233198#M6027</link>
      <description>I did not mention above. The NSR N1200 was a second hand unit that came out of a working site. The unit should be fully functional but I can not guarantee that 100%</description>
      <pubDate>Mon, 29 Mar 2004 19:48:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/connecting-msl5030-to-windows-2000/m-p/3233198#M6027</guid>
      <dc:creator>Lloyd_10</dc:creator>
      <dc:date>2004-03-29T19:48:26Z</dc:date>
    </item>
    <item>
      <title>Re: Connecting MSL5030 to windows 2000</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/connecting-msl5030-to-windows-2000/m-p/3233199#M6028</link>
      <description>I was wrong. The servers do not see the Ultriam (LTO) drives. They are in removable media with crosses through they.</description>
      <pubDate>Tue, 30 Mar 2004 01:18:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/connecting-msl5030-to-windows-2000/m-p/3233199#M6028</guid>
      <dc:creator>Lloyd_10</dc:creator>
      <dc:date>2004-03-30T01:18:00Z</dc:date>
    </item>
    <item>
      <title>Re: Connecting MSL5030 to windows 2000</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/connecting-msl5030-to-windows-2000/m-p/3233200#M6029</link>
      <description>You should disable Removable storage in order to use another Backup SW or it will keep ownership of the devices</description>
      <pubDate>Tue, 30 Mar 2004 01:48:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/connecting-msl5030-to-windows-2000/m-p/3233200#M6029</guid>
      <dc:creator>Marino Meloni_1</dc:creator>
      <dc:date>2004-03-30T01:48:12Z</dc:date>
    </item>
    <item>
      <title>Re: Connecting MSL5030 to windows 2000</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/connecting-msl5030-to-windows-2000/m-p/3233201#M6030</link>
      <description>Thanks.&lt;BR /&gt;&lt;BR /&gt;I disabled the service then rebooted but still had the same result</description>
      <pubDate>Tue, 30 Mar 2004 02:05:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/connecting-msl5030-to-windows-2000/m-p/3233201#M6030</guid>
      <dc:creator>Lloyd_10</dc:creator>
      <dc:date>2004-03-30T02:05:20Z</dc:date>
    </item>
    <item>
      <title>Re: Connecting MSL5030 to windows 2000</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/connecting-msl5030-to-windows-2000/m-p/3233202#M6031</link>
      <description>best practice ask to disable RMS to any w2k W2K3 servers that could access to the device on the san&lt;BR /&gt;also:&lt;BR /&gt;set robotic with SCSI id 1&lt;BR /&gt;set drives with SCSI id 2 and 3&lt;BR /&gt;make sure  the Command Console lun is mapped to LUN 0&lt;BR /&gt;library controller is mapped to lun1&lt;BR /&gt;drives are mapped as lun 2 and 3&lt;BR /&gt;&lt;BR /&gt;be sure to have latest fw on library and on nsr&lt;BR /&gt;&lt;BR /&gt;then run again the Arvserve configuration</description>
      <pubDate>Tue, 30 Mar 2004 02:59:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/connecting-msl5030-to-windows-2000/m-p/3233202#M6031</guid>
      <dc:creator>Marino Meloni_1</dc:creator>
      <dc:date>2004-03-30T02:59:22Z</dc:date>
    </item>
    <item>
      <title>Re: Connecting MSL5030 to windows 2000</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/connecting-msl5030-to-windows-2000/m-p/3233203#M6032</link>
      <description>Lloyd,&lt;BR /&gt;&lt;BR /&gt;If Arcserve can't see the devices you can use the native drivers provided by HP for the Changer and drives.&lt;BR /&gt;&lt;BR /&gt;Download from the following link and exexute the program which will detect the attached MSL5030 drives and robotic controller. This might resolve the problem as you should then be able to see the devices in W2K device manager under Changers and Tape Drives.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="ftp://ftp.compaq.com/pub/products/storageworks/tape_drivers/" target="_blank"&gt;ftp://ftp.compaq.com/pub/products/storageworks/tape_drivers/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I hope this helps,&lt;BR /&gt;&lt;BR /&gt;Brian&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 30 Mar 2004 03:34:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/connecting-msl5030-to-windows-2000/m-p/3233203#M6032</guid>
      <dc:creator>Brian_Murdoch</dc:creator>
      <dc:date>2004-03-30T03:34:17Z</dc:date>
    </item>
    <item>
      <title>Re: Connecting MSL5030 to windows 2000</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/connecting-msl5030-to-windows-2000/m-p/3233204#M6033</link>
      <description>Lloyd,&lt;BR /&gt;&lt;BR /&gt;did you check the SCSI mapping on the new NSR? If I recall it correctly, the "old" MDR automatically made all found SCSI devices available whereas the NSRs have to be configured explicitely. Looks to me like this problem as you write that you can see the NSR itself but not the connected devices ...&lt;BR /&gt;&lt;BR /&gt;Urban</description>
      <pubDate>Wed, 31 Mar 2004 02:20:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/connecting-msl5030-to-windows-2000/m-p/3233204#M6033</guid>
      <dc:creator>Urban Petry</dc:creator>
      <dc:date>2004-03-31T02:20:19Z</dc:date>
    </item>
    <item>
      <title>Re: Connecting MSL5030 to windows 2000</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/connecting-msl5030-to-windows-2000/m-p/3233205#M6034</link>
      <description>The most common problem is not filling in a NSR map and assigning it to the specific hosts that need to see the devices.&lt;BR /&gt;&lt;BR /&gt;You want to setup the network interface (if you haven't already) and use the web management interface to do the setup. &lt;BR /&gt;&lt;BR /&gt;The preference is to use an indexed map. That's the default, however the map is initially empty (so you don't see the devices). You need to fill the map and also assign it to the host(s) (the wwn's of the HBAs that need to see the devices).&lt;BR /&gt;</description>
      <pubDate>Wed, 31 Mar 2004 09:42:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/connecting-msl5030-to-windows-2000/m-p/3233205#M6034</guid>
      <dc:creator>David Ruska</dc:creator>
      <dc:date>2004-03-31T09:42:57Z</dc:date>
    </item>
    <item>
      <title>Re: Connecting MSL5030 to windows 2000</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/connecting-msl5030-to-windows-2000/m-p/3233206#M6035</link>
      <description>Thanks everyone.&lt;BR /&gt;&lt;BR /&gt;they were all valid and good suggestions. The issue I had was what David and Petry suggested. I needed to manually map out the devices in the MDR. Now I can see the changer and both drives in Arcserve.&lt;BR /&gt;&lt;BR /&gt;Thanks for your help.&lt;BR /&gt;&lt;BR /&gt;Lloyd</description>
      <pubDate>Thu, 01 Apr 2004 01:33:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/connecting-msl5030-to-windows-2000/m-p/3233206#M6035</guid>
      <dc:creator>Lloyd_10</dc:creator>
      <dc:date>2004-04-01T01:33:21Z</dc:date>
    </item>
  </channel>
</rss>

