Jump to content
Sign in to follow this  
slapidus

Retrospect Script w/Windows Asleep

Recommended Posts

I've now successfully written a script to initiate Normal and Recycle backups; however, scripts don't initiate when Windows is in screen saver and hybernation modes. Is there any way to overcome this problem without disabling screen saver and hybernation? Thanks.

 

Steve

Share this post


Link to post
Share on other sites

Hi

 

Retrospect will not launch when the machine is asleep, in hybernation mode or powered off. The screen saver should not make a difference.

 

Monitor sleep and disk sleep are not a problem. When the whole machine goes to standby mode is where the trouble begins.

 

Your best bet is to disable hybernation/standby and set Retrospect to shutdown the machine after the backup is finished.

 

Thanks

nate

Share this post


Link to post
Share on other sites

Natew,

 

Hi

 

Any change on this issue with 6.5.350?

When I view client properties and ask for a refresh, sometimes it comes to life in-time to respond, other times it takes more than once after the issuance of the "client not found" warning.

 

Any setting availible to extend the time retro waits for a client to wake during backup?

Any difference in the way retro performs this between manual and proactive?

Share this post


Link to post
Share on other sites

Hi

 

No changes have been made in this regard. Retrospect uses multicast to look for clients when it runs a backup. If Retrospect woke up clients it would have to wake up every client machine on the network every time a script ran. That means your machines would probably be on all night anyway...

 

Nate

Share this post


Link to post
Share on other sites

I made this work using external scripting. Here's my RetroEventHandler.bat file:

 

@echo off

set _PROC=%1

shift

goto :%_PROC%

:StartApp

goto :EXIT

:EndApp

goto :EXIT

:StartBackupServer

goto :EXIT

:StopBackupServer

goto :EXIT

:StartScript

call wake %1

ask /n /ty,60 Pausing to wait for Retrospect client to start on %1 ...

goto :EXIT

:EndScript

goto :EXIT

:StartSource

goto :EXIT

:EndSource

goto :EXIT

:MediaRequest

goto :EXIT

:TimedOutMediaRequest

goto :EXIT

:ScriptCheckFailed

goto :EXIT

:NextExec

goto :EXIT

:StopSched

goto :EXIT

:PasswordEntry

goto :EXIT

:FatalBackupError

goto :EXIT

:EXIT

 

 

and here's wake.bat:

 

@echo off

If %1==bc goto :bc

 

If %1=="bc" goto :bc

If %1==bcronin goto :bcronin

If %1=="bcronin" goto :bcronin

If %1==mac goto :mac

If %1=="mac" goto :mac

If %1==pcronin goto tongue.gifcronin

If %1=="pcronin" goto tongue.gifcronin

goto :exit

:bc

wolcmd 00e018fc63ef 192.168.0.101 255.255.255.0

goto :exit

:bcronin

wolcmd 000ea61e69cc 192.168.0.100 255.255.255.0

goto :exit

:mac

wolcmd 000A95B0553A 192.168.0.103 255.255.255.0

goto :exit

tongue.gifcronin

wolcmd 00e01899c890 192.168.0.102 255.255.255.0

:exit

 

 

Wolcmd I got from:

 

http://www.depicus.com/wake-on-lan/

 

Ok, so it is a bit tedious having to enumerate the MAC addresses of all the clients in the bat file, but I only had a few clients so it wasn't worth doing anything more clever.

 

The only fly left in the ointment for me is that the "bc" client regularly falls back asleep DURING a backup (something I am pursuing on another thread herein).

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×