Direkt zum Inhalt

Backup to a shared drive on another computer

Thread needs solution

I am already using ATI Home to backup files to a shared folder on another computer.

Until now, I always played safe with the other computer by manually turning off its sleep function.

But my main question is: if ATI is "connected" to the drive on the other computer, is that enough "activity" to prevent the respective computer from going to sleep?

Another question is: is it possible for ATI Home to send a WOL packet to wakeup the other computer? a) when the backup starts? and b) during the backup (related to my main question above)?

AndrewFG

0 Users found this helpful
Andrew Fiddian-Green wrote:
...my main question is: if ATI is "connected" to the drive on the other computer, is that enough "activity" to prevent the respective computer from going to sleep?

Which operating system is being used on the computer that you're saving the backup to? If Windows XP, yes. If Vista or Windows 7, probably not. The newer operating systems look for user activity (mouse and/or keyboard) and if none is detected within 2 minutes after waking, they will go back to sleep. You would need to work around this.

Another question is: is it possible for ATI Home to send a WOL packet to wakeup the other computer? a) when the backup starts? and b) during the backup (related to my main question above)?

For a), yes. For b), it won't do any good. If the PC is currently awake then it will ignore the WOL packet.

To send a WOL packet you would need to create a batch file that is called by TI as a pre-execution task. This batch file would need to send a WOL packet and then wait long enough for the PC to resume from sleep mode. To send a WOL packet, download the WOLCMD.exe file from http://www.depicus.com

K0LO wrote:
You would need to work around this.

Any suggestions?

To send a WOL packet you would need to create a batch file that is called by TI as a pre-execution task

I don't see any way (ATI Home 2009) to call a batch file. Am I missing something?

AndrewFG

To work around the sleep issue you would need to get creative. If you're using Windows 7, any scheduled task that is triggered will run to completion (Vista needs a patch to work this way). Perhaps you could set up a dummy task that is triggered each time that the PC resumes from sleep and either waits for network activity to cease, or just waits for a predetermined length of time.

Batch files can be run as pre-execution or post-execution tasks in TI. I don't have the appropriate screen shots available for TI 2009; these are from TI 10. When setting up a backup using the Backup Wizard, you need to choose "Set the options manually":

Then on the Backup Creation Options screen, choose the batch file(s) desired:

There are timing issues to solve; you obviously need to wait long enough for the target PC to come out of standby before sending a backup its way, so you may have better luck by scripting the entire backup process. Have the script wake the target PC, wait until it's up and running, then run the backup task by calling TI from a command prompt.

Anhang Größe
12982-86461.PNG 55.89 KB
12982-86464.PNG 72.87 KB

as for "a"
ATI lets you call any ".bat" file you want as a "before" backup task and another as a "post" backup task. the backup itself does not officially begin until the "pre" backup job finishes.
To call a batch from an ATI job simply list it in the panel found in "backup options" "pre/post command".
As for what you put in that ".bat" file it your call as its your code not ATI code.

as for "b"
This is your code not ATI code. I have both pre and post backup tasks in my ATI jobs however none of them need to do what you are talking about here. I can guess what your might look like but its really yours to write. If I had to guess it would be a total of three batch files.
"#1" is your main pre-task batch file it does the first WOL, makes sure a "stop" file does NOT exist and then starts up #2 as a seperate process/window and exits.
The fact that #1 exits means the actual ATI backup can now begin.
"#2" is an endless loop of - check if "stop" file exists if not send WOL,sleep a bit, repeat.
"#3" is a POST task batch file that creates a "stop" file for number 2 to see, delete the stop file and exit itself so the stream of WOL's end.

Dear Kolo / Dear oracledba,

Thanks for both of your suggestions.
I will give it a try.

AndrewFG