Ask the Community
Groups
Data Copy Access (DCA) job power-on timeout failure - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>Data copy access (DCA) job fails to detect the heart beat for one or many instant recovery VMs.</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p>A Data Copy Access (DCA) job inaccurately reports one or many instant recovery VMs fail to boot. Review of the state of each VMIR reveals that they have booted up successfully.</p> <h2 data-id="resolution"><strong>RESOLUTION</strong></h2> <p>To work around this problem, modify the registry for the production VM to increase the default time-out value for the service control manager. To increase this value to 1800 seconds (30 minutes), follow these steps:<br> </p> <ol><li>Click <strong>Start</strong>, click <strong>Run</strong>, type regedit, and then click <strong>OK</strong>.</li> <li>Locate and then click the following registry subkey:<br><strong>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control</strong> </li> <li>In the right pane, locate the <strong>ServicesPipeTimeout</strong> entry.<br><br> Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps:<br> <ol><li>On the <strong>Edit</strong> menu, point to <strong>New</strong>, and then click <strong>DWORD Value</strong>.</li> <li>Type ServicesPipeTimeout, and then press ENTER.<br> </li> </ol></li> <li>Right-click <strong>ServicesPipeTimeout</strong>, and then click <strong>Modify</strong>.</li> <li>Click <strong>Decimal</strong>, type 1800000, and then click <strong>OK</strong>.<br><br> This value represents the time in milliseconds before a service times out. Note This change does not take effect until the computer is restarted.</li> <li>Take another backup (new full not necessary)</li> <li>Wait for the backup to replicate If running the DCA job from a target appliance.</li> <li>Re-attempt the Data Copy Access (DCA) job.</li> </ol><h2 data-id="cause"><strong>CAUSE</strong></h2> <p>Either VMware tools or Hyper-V integration services did not start which has prevented the VM guest heart beat from being detected.<br> </p> <h2 data-id="notes"><strong>NOTES</strong></h2> <p><a href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fsupport.microsoft.com%2Fkb%2F922918">http://support.microsoft.com/kb/922918</a></p> </article> </main>