Pro v7 job fails because destination takes too long to spin up

[gn33101]

I'm running a mirror job to a network destination.
The destination drives sleeps when not in use.

When the Syncback job runs, the drive does not come online fast enough and I always get a 'destination scan failed' error.

Does anybody have a method to query or wake up the network drive before the Syncback job runs?
Or maybe increase the timeout on the destination scan?

Many Thanks!

[Swapna]

Hi,

Does anybody have a method to query or wake up the network drive before the Syncback job runs?

You can write a batch/script file that uses the 'Wake ON LAN' event to wake the remote computer and call this in the Program-Before section of the profile run. You can refer to this forum post for more details:

viewtopic.php?f=29&p=46720   

Or maybe increase the timeout on the destination scan?

You can add a short delay under:

Modify > When > Misc > Pause for X seconds option

Please read the help file for more details on this option. With Misc settings page opened, press F1 to open the contextual help.  

Thank you.

[sayani65]

Encountering a Pro v7 job failure due to a delayed destination spin-up prompts contemplation on optimizing hardware and system responsiveness. Users may explore solutions such as adjusting startup times or ensuring adequate resources, seeking a balance between efficient operations and the reliability of the destination.