<?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: Vmdk file is not connected in VMware vCenter™ Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498699#M7523</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;size in BYTES please&lt;BR /&gt;check via ssh or winscp please&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 04 Feb 2019 15:41:22 GMT</pubDate>
    <dc:creator>continuum</dc:creator>
    <dc:date>2019-02-04T15:41:22Z</dc:date>
    <item>
      <title>Vmdk file is not connected</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498686#M7510</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There was a virtual machine. 2 disks were connected to it. One disk was located on the external storage of another on the server itself. After an incorrect reboot. The virtual machine did not start and gave an error. Error below.&lt;/P&gt;&lt;P&gt;The disk that was located on the storage from the virtual machine was disconnected. When you try to man it again, the system does not see it. Although the VMDK dilation file. In Vcentre, the Type shows File, and on other similar disks the type is Virtual disk.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unable to access virtual disk 'Hard disk 2' from the host. Either the host is disconnected from the datastore or has insufficient privilege. Details: Unable to access file [Backup] Backup-SRV/Backup-SRV.vmdk&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Feb 2019 06:37:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498686#M7510</guid>
      <dc:creator>Viktor_2018</dc:creator>
      <dc:date>2019-02-01T06:37:02Z</dc:date>
    </item>
    <item>
      <title>Re: Vmdk file is not connected</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498687#M7511</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If&amp;nbsp; you have access to connect to ESXi , kindly check if the host is able to see the respective LUN. Rescan the storage for that host&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Feb 2019 06:57:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498687#M7511</guid>
      <dc:creator>swathimp</dc:creator>
      <dc:date>2019-02-01T06:57:24Z</dc:date>
    </item>
    <item>
      <title>Re: Vmdk file is not connected</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498688#M7512</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Scanned storage! Connect the LUN to another server. The problem repeats. Most likely a problem with the file.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Feb 2019 07:04:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498688#M7512</guid>
      <dc:creator>Viktor_2018</dc:creator>
      <dc:date>2019-02-01T07:04:30Z</dc:date>
    </item>
    <item>
      <title>Re: Vmdk file is not connected</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498689#M7513</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you share the below:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Datastore Status&lt;/LI&gt;&lt;LI&gt;Browse the content of the VM folder with details in the datastore&lt;/LI&gt;&lt;LI&gt;VM settings specially for this virtual disk&lt;/LI&gt;&lt;LI&gt;Error when Turn on the VM&lt;/LI&gt;&lt;/UL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Feb 2019 07:37:31 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498689#M7513</guid>
      <dc:creator>HassanAlKak88</dc:creator>
      <dc:date>2019-02-01T07:37:31Z</dc:date>
    </item>
    <item>
      <title>Re: Vmdk file is not connected</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498690#M7514</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Error&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif;"&gt;Unable to access virtual disk 'Hard disk 2' from the host. Either the host is disconnected from the datastore or has insufficient privilege. Details: Unable to access file [Backup] Backup-SRV/Backup-SRV.vmdk&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Feb 2019 07:49:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498690#M7514</guid>
      <dc:creator>Viktor_2018</dc:creator>
      <dc:date>2019-02-01T07:49:38Z</dc:date>
    </item>
    <item>
      <title>Re: Vmdk file is not connected</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498691#M7515</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You mentioned that you mapped this LUN to other server, can you more explain what happened in this scenario ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Feb 2019 08:47:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498691#M7515</guid>
      <dc:creator>HassanAlKak88</dc:creator>
      <dc:date>2019-02-01T08:47:36Z</dc:date>
    </item>
    <item>
      <title>Re: Vmdk file is not connected</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498692#M7516</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I compared this LUN with another server and the problem is the same. The system does not see the VMDK when added to a virtual machine.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Feb 2019 10:24:53 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498692#M7516</guid>
      <dc:creator>Viktor_2018</dc:creator>
      <dc:date>2019-02-01T10:24:53Z</dc:date>
    </item>
    <item>
      <title>Re: Vmdk file is not connected</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498693#M7517</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;First step, please confirm that the new server see the LUN as datastore after the mapping. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;then we will see the status of vmdk.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;please advise,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Feb 2019 10:44:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498693#M7517</guid>
      <dc:creator>HassanAlKak88</dc:creator>
      <dc:date>2019-02-01T10:44:36Z</dc:date>
    </item>
    <item>
      <title>Re: Vmdk file is not connected</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498694#M7518</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here you can see on the pictures that LUN is connected to ESXI 2. But when mounted on any of the servers on this ESXI, the problem repeats.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Feb 2019 10:52:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498694#M7518</guid>
      <dc:creator>Viktor_2018</dc:creator>
      <dc:date>2019-02-01T10:52:45Z</dc:date>
    </item>
    <item>
      <title>Re: Vmdk file is not connected</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498695#M7519</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; Details: Unable to access file [Backup] Backup-SRV/Backup-SRV.vmdk&lt;BR /&gt;That is because the mentioned file is not there !&lt;BR /&gt;You only have the flat.vmdk - so you must create a new descriptor vmdk.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Feb 2019 15:55:30 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498695#M7519</guid>
      <dc:creator>continuum</dc:creator>
      <dc:date>2019-02-01T15:55:30Z</dc:date>
    </item>
    <item>
      <title>Re: Vmdk file is not connected</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498696#M7520</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I speak english badly. Therefore, Skype does not work. Is there a description of the VMDK files? And what could have affected the file being damaged?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Feb 2019 12:34:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498696#M7520</guid>
      <dc:creator>Viktor_2018</dc:creator>
      <dc:date>2019-02-04T12:34:45Z</dc:date>
    </item>
    <item>
      <title>Re: Vmdk file is not connected</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498697#M7521</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;post size in bytes and exact name of the flat.vmdk&lt;BR /&gt;then I will create the descriptor for you&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Feb 2019 13:20:34 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498697#M7521</guid>
      <dc:creator>continuum</dc:creator>
      <dc:date>2019-02-04T13:20:34Z</dc:date>
    </item>
    <item>
      <title>Re: Vmdk file is not connected</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498698#M7522</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Name:&amp;nbsp; Backup-SRV-flat.vmdk&lt;/P&gt;&lt;P&gt;Size: 2 097 152 000 Kb&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Feb 2019 14:08:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498698#M7522</guid>
      <dc:creator>Viktor_2018</dc:creator>
      <dc:date>2019-02-04T14:08:48Z</dc:date>
    </item>
    <item>
      <title>Re: Vmdk file is not connected</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498699#M7523</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;size in BYTES please&lt;BR /&gt;check via ssh or winscp please&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Feb 2019 15:41:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498699#M7523</guid>
      <dc:creator>continuum</dc:creator>
      <dc:date>2019-02-04T15:41:22Z</dc:date>
    </item>
    <item>
      <title>Re: Vmdk file is not connected</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498700#M7524</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Which command displays the file size in bytes in ssh?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Feb 2019 11:17:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498700#M7524</guid>
      <dc:creator>Viktor_2018</dc:creator>
      <dc:date>2019-02-08T11:17:15Z</dc:date>
    </item>
    <item>
      <title>Re: Vmdk file is not connected</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498701#M7525</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #545454; font-family: arial, sans-serif; font-size: small;"&gt;On attempting to pair a server by using a hyper visor &lt;/SPAN&gt;&lt;SPAN style="font-weight: bold; color: #6a6a6a; font-family: arial, sans-serif; font-size: small;"&gt;connection&lt;/SPAN&gt;&lt;SPAN style="color: #545454; font-family: arial, sans-serif; font-size: small;"&gt; with your Datto backup appliance, or when attempting to perform a backup of a system protected with the agent less backup solution&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #545454; font-family: arial, sans-serif; font-size: small;"&gt;&lt;SPAN data-sheets-userformat="{&amp;quot;2&amp;quot;:833,&amp;quot;3&amp;quot;:{&amp;quot;1&amp;quot;:0},&amp;quot;9&amp;quot;:0,&amp;quot;11&amp;quot;:3,&amp;quot;12&amp;quot;:0}" data-sheets-value="{&amp;quot;1&amp;quot;:2,&amp;quot;2&amp;quot;:&amp;quot;shareit&amp;quot;}" style="font-size: 10pt; font-family: Arial;"&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Feb 2019 10:16:01 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498701#M7525</guid>
      <dc:creator>admin</dc:creator>
      <dc:date>2019-02-19T10:16:01Z</dc:date>
    </item>
    <item>
      <title>Re: Vmdk file is not connected</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498702#M7526</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When attempting to associate a VMDK disk with a virtual machine. Previously, this disk was connected to the virtual machine that was performing the backup.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Feb 2019 12:08:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Vmdk-file-is-not-connected/m-p/498702#M7526</guid>
      <dc:creator>Viktor_2018</dc:creator>
      <dc:date>2019-02-20T12:08:12Z</dc:date>
    </item>
  </channel>
</rss>

