<?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: Unable to Complete Backup of Virtual Machine Using Veeam in Backup &amp; Recovery Discussions</title>
    <link>https://communities.vmware.com/t5/Backup-Recovery-Discussions/Unable-to-Complete-Backup-of-Virtual-Machine-Using-Veeam/m-p/2933316#M18705</link>
    <description>&lt;P&gt;This has been resolved.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Veeam was reporting a locked file, it was actually Veeam not being able to communicate on Port 902 to two of our three hosts due to a network configuration issue.&lt;/P&gt;</description>
    <pubDate>Wed, 12 Oct 2022 20:17:42 GMT</pubDate>
    <dc:creator>csharpe1</dc:creator>
    <dc:date>2022-10-12T20:17:42Z</dc:date>
    <item>
      <title>Unable to Complete Backup of Virtual Machine Using Veeam</title>
      <link>https://communities.vmware.com/t5/Backup-Recovery-Discussions/Unable-to-Complete-Backup-of-Virtual-Machine-Using-Veeam/m-p/2931762#M18704</link>
      <description>&lt;P&gt;Trying to backup a Virtual Machine and it is stopping, stating that there is a locked file. I can backup the machine while offline.&lt;/P&gt;&lt;P&gt;Veeam logs show the following:&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;SPAN&gt;[01.10.2022 02:16:02] &amp;lt;40&amp;gt; Error Failed to prepare VM for processing: DiskLib error: [13].The file is locked or in use -- File open failed: File not open&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;[01.10.2022 02:16:02] &amp;lt;40&amp;gt; Error --tr:Failed to start file downloading. VMFS path: [[storagename] VMNAME/VMNAME.vmx].&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I've reached out to Veeam support and they are saying that there is a vmx.lck file (and there is), which is causing the lock and to contact VMWare, but from what I can tell, that is normally in place for a running VM. Other VM running on the same storage and host are backing up correctly while running.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've tried the following to correct the issue:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Restarting the host&lt;/LI&gt;&lt;LI&gt;Migrating the VM to a different host&lt;/LI&gt;&lt;LI&gt;Migrating the VM to a different storage device&lt;/LI&gt;&lt;LI&gt;Restarting vCenter&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Mon, 03 Oct 2022 18:00:27 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Backup-Recovery-Discussions/Unable-to-Complete-Backup-of-Virtual-Machine-Using-Veeam/m-p/2931762#M18704</guid>
      <dc:creator>csharpe1</dc:creator>
      <dc:date>2022-10-03T18:00:27Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to Complete Backup of Virtual Machine Using Veeam</title>
      <link>https://communities.vmware.com/t5/Backup-Recovery-Discussions/Unable-to-Complete-Backup-of-Virtual-Machine-Using-Veeam/m-p/2933316#M18705</link>
      <description>&lt;P&gt;This has been resolved.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Veeam was reporting a locked file, it was actually Veeam not being able to communicate on Port 902 to two of our three hosts due to a network configuration issue.&lt;/P&gt;</description>
      <pubDate>Wed, 12 Oct 2022 20:17:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Backup-Recovery-Discussions/Unable-to-Complete-Backup-of-Virtual-Machine-Using-Veeam/m-p/2933316#M18705</guid>
      <dc:creator>csharpe1</dc:creator>
      <dc:date>2022-10-12T20:17:42Z</dc:date>
    </item>
  </channel>
</rss>

