Ask the Community
Groups
-- Error opening the disk ; The handle is invalid - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>Error opening the disk in ReliableDR Replication jobs</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <div>This problem occurs rarely on ReliableDR Replication jobs and is visible on debug view window.</div> <div>During the test could happen that some VMs internal files are locked for exclusive use, so the open or read attempts will fail.</div> <div> </div> <div><img alt="1__1_.png" src="https://phdreliabledr.zendesk.com/attachments/token/protxauudhzix60/?name=1+%281%29.png" class="embedImage-img importedEmbed-img"></img></div> <div> </div> <div> </div> <div> <div>ReliableDR retries the operation before giving up on the replication job, sometimes succeeding other times failing.</div> <div> </div> <div>The number of retries is established on settings window.</div> <div> </div> <div> </div> <div><img alt="settings_retries.png" src="https://phdreliabledr.zendesk.com/attachments/token/tmj6hh9mfdfddon/?name=settings_retries.png" class="embedImage-img importedEmbed-img"></img></div> <div> </div> <div> <strong>If the problem persists</strong> there is still a couple of things to try:</div> <div> </div> <div> <ul><li>It could be related with the ReliableDR connectivity requirements: </li></ul><div><a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Funitrends-support.zendesk.com%2Fhc%2Fen-us%2Farticles%2F360013157157">ReliableDR connectivity requirements</a></div> </div> <div>ReliableDR also needs DNS resolution of all ESX hosts (source/primary) involved in the replication if they are added to the vCenter via the hostname.</div> <div> </div> <div> <ul><li>Enter ReliableDR server and check VDDK logs at C:\WINDOWS\Temp\vmware-SYSTEM, if you see this error:</li></ul></div> <div> <p><em>Error: Not licensed to use this function. Error 16064 at 2357</em></p> </div> <div>The problem is that vCenter user has not permissions at vCenter top level, see this VMware kbase article for more information:</div> <div><a rel="nofollow" href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fkb.vmware.com%2Fselfservice%2Fmicrosites%2Fsearch.do%3Flanguage%3Den_US%26cmd%3DdisplayKC%26externalId%3D2063054">http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2063054</a></div> <div> </div> <div> </div> <div> </div> <div> </div> </div> </article> </main>