Hi,

What steps it completed before 'to target operating system' ?

This error says that the client did not contact the server after a reboot. Is Ghost agent running in the client?

Krish 

Here are the steps produced from the log file results from the backup regime failure:

Wake-on-LAN
Client file missing - copying from server now
Update DOS system files
Update DOS Network drivers
Changing Logon Settings
To target operating system

Everything had a "success" status prior to the "to target operating system" event which had a status of "fail"

 Hi,

At this point, it should restart the system to take a snapshot. It is expecting the client to contact server after the reboot, but it has not happened. Probably it would say 'Time out' under the details of failed task. It is difficult to think of any specific reason for it to fail, does client shown as connected in Console after this fails? Is there anything in the Windows event log?

Krish

Thanks for the reply,

Its hard for me to tell if client is showing as connected because I am running the backup at 11pm. Last night I remoted into my PC where I have the Ghost Console installed and running the scheduled task to do the backup regime and noticed it had failed at the exact same step...however, when I run the same backup regime manually, it ran fine through to completion. So, its like the backup regime will run if I start it manually, but not when it is initiated through the schedule.

When I look at the event log for the scheduled backup regime, the Event Details for the step that failed (To target operating system) says "Client Timed Out"

Why would the client time out when it is initiated with the scheduled task but not when I initiate it manually?

Jeff

 Hi,

That is very good information. It may be the clients condition at the time backup runs. If it is at 11.00pm, most likely client is in hibernation or at sleep. There are couple of things come to my mind. One is WOL is not working properly, or some machine behave differently when boot up with WOL. Second thing is something preventing rebooting the client when no one is logged in. That could explain why it is working when you run manually. 

Other difference is when running through the scheduler it is running under a different user context. This should not affect the client, but you can schedule a task to run during the day (in couple of minutes) and see what's going to happen.

Krish

I looked at the laptop and it had "hibenation" enabled so I'm thinking this might be the issue...I have disabled hibernation and will see how it runs this evening