<?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: How to clear SD6.2 config where luns are on a non accessible iscsi portal ? in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/How-to-clear-SD6-2-config-where-luns-are-on-a-non-accessible-iscsi-portal/m-p/69506#M8875</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's not possible to remove the source host in such a case, since snapdrive considers it is the local host.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I found out why snapdrive was connecting to the old server instead of the local server: it's because it uses the hostname and there was an issue with name resolution.&lt;/P&gt;&lt;P&gt;When the customer restored the server, he changed the ip adress and didn't integrate the AD, but he forgot to change the local hosts file in c:\windows\system32\drivers\etc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After changing this, it works well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Regis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 13 Jan 2011 16:23:40 GMT</pubDate>
    <dc:creator>garruche</dc:creator>
    <dc:date>2011-01-13T16:23:40Z</dc:date>
    <item>
      <title>How to clear SD6.2 config where luns are on a non accessible iscsi portal ?</title>
      <link>https://community.netapp.com/t5/Data-Protection/How-to-clear-SD6-2-config-where-luns-are-on-a-non-accessible-iscsi-portal/m-p/69489#M8872</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IHAC who restored a Windows 2008 server on a new site, where there are snapmirror copies of its luns that can be connected through iSCSI.&lt;/P&gt;&lt;P&gt;These copies are intended to work independently from original luns and server. So original luns and source storage are still on the network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the restored server, IQN has been changed and target portal to source storage has been removed, so the restored server can ping and connect through HTTP on the source storage.&lt;/P&gt;&lt;P&gt;But, this restored server has no access to source luns, which what we want.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem:&lt;/P&gt;&lt;P&gt;While this restored server has no access to the original source iSCSI portal, Snapdrive still shows the old luns.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The luns are not connected to the new server (you can't see them in Disk Management) but they show up in Snapdrive.&lt;/P&gt;&lt;P&gt;If we try to disconnect them from Snapdrive on the new server, then the lun is unmapped on the original server and not on the restored server.....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We try to uninstall SD and install it again. Every time, old luns show up even if there is no connection available to orignal luns.&lt;/P&gt;&lt;P&gt;Snapdrive versions are 6.2 or 6.2P1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is:&lt;/P&gt;&lt;P&gt;how can we clear the configuration of snapdrive so all previously connected luns don't show up again in Snapdrive GUI ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you in advance for any answer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:02:27 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/How-to-clear-SD6-2-config-where-luns-are-on-a-non-accessible-iscsi-portal/m-p/69489#M8872</guid>
      <dc:creator>garruche</dc:creator>
      <dc:date>2025-06-05T07:02:27Z</dc:date>
    </item>
    <item>
      <title>Re: How to clear SD6.2 config where luns are on a non accessible iscsi portal ?</title>
      <link>https://community.netapp.com/t5/Data-Protection/How-to-clear-SD6-2-config-where-luns-are-on-a-non-accessible-iscsi-portal/m-p/69493#M8873</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What can you tell me about the host that was restored on the Mirrored side? Is the host name the same? Did they run sysprep?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It sounds to me like SnapDrive on this new host at the mirrored side is managing the original host. There is nothing preventing you from mapping / unmapping LUNs from both systems through the centralized interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If your customer does not want to see or manage the other (original) host I’d right-click on the original server name in that left-hand window and disconnect from that server.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Jan 2011 15:33:58 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/How-to-clear-SD6-2-config-where-luns-are-on-a-non-accessible-iscsi-portal/m-p/69493#M8873</guid>
      <dc:creator>jalmanza</dc:creator>
      <dc:date>2011-01-11T15:33:58Z</dc:date>
    </item>
    <item>
      <title>Re: How to clear SD6.2 config where luns are on a non accessible iscsi portal ?</title>
      <link>https://community.netapp.com/t5/Data-Protection/How-to-clear-SD6-2-config-where-luns-are-on-a-non-accessible-iscsi-portal/m-p/69501#M8874</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Joe,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The hostname will be the same for a while, but they don't have the same IP.&lt;/P&gt;&lt;P&gt;They didn't use sysprep but a software that restore systems (Evault from i365).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So you mean that it doesn't manage the destination host but the source host. You may be right.&lt;/P&gt;&lt;P&gt;Tomorrow, I will try to remove the management of that host.&lt;/P&gt;&lt;P&gt;Thank you for the idea: I didn't think to that at all because they have the same name.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another idea: what if I stop the Snapdrive Manager service (not the snapdrive service) ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Jan 2011 13:38:18 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/How-to-clear-SD6-2-config-where-luns-are-on-a-non-accessible-iscsi-portal/m-p/69501#M8874</guid>
      <dc:creator>garruche</dc:creator>
      <dc:date>2011-01-12T13:38:18Z</dc:date>
    </item>
    <item>
      <title>Re: How to clear SD6.2 config where luns are on a non accessible iscsi portal ?</title>
      <link>https://community.netapp.com/t5/Data-Protection/How-to-clear-SD6-2-config-where-luns-are-on-a-non-accessible-iscsi-portal/m-p/69506#M8875</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's not possible to remove the source host in such a case, since snapdrive considers it is the local host.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I found out why snapdrive was connecting to the old server instead of the local server: it's because it uses the hostname and there was an issue with name resolution.&lt;/P&gt;&lt;P&gt;When the customer restored the server, he changed the ip adress and didn't integrate the AD, but he forgot to change the local hosts file in c:\windows\system32\drivers\etc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After changing this, it works well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Regis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Jan 2011 16:23:40 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/How-to-clear-SD6-2-config-where-luns-are-on-a-non-accessible-iscsi-portal/m-p/69506#M8875</guid>
      <dc:creator>garruche</dc:creator>
      <dc:date>2011-01-13T16:23:40Z</dc:date>
    </item>
  </channel>
</rss>

