Client machines do not shut down
I am using ABR 10 #12457 and i have a problem while doing the nightly backup. The client pc's (XP SP3) are waked up with WOL successfully, are backed up, but they do not shut down after the backup.
Any hints for this issue ?
Greetings
Ralf

- Log in to post comments

Hello, I am using ABR 10 #11639 and I have an opposite problem on my PCs.
I need to do daily backup, as planned,
after this start the validation step of this backup,
and after validation-end the switch-off the PC for night-time.
The backup-plan is so configured, with automatic shutdown .bat declared as shown in your Acronis/articlear, very clear, in the "Pre/Post command Section" , field "Execute after backup".
The problem:
The automatic shutdown start regulary a few seconds after back-up end,
and so the validation step (already started in the meantime as planned..) is TRUNCATED on-fly!!
The solution (?)
Which is the right way to obtain the shutdown only AFTER validation-end ?
Thanks to all for any help
- Log in to post comments

Hello Sergio,
Thank you very much for your post. I will definitely help you with this issue.
Our program was designed in such a way, that the backup and validation are run as separate tasks. The pre/post commands run after the backup tasks are completed. However, I can offer you the following workaround:
1. You can estimate approximately how long the validation task runs on your computer and include a command into the shutdown batch file, which will postpone the shutdown for the amount of time needed for validation. For example, sleep or timeout commands can be used if you have Windows Resource Kit installed on your computer.
2, If you do not have Windows Resource Kit, you can try using ping or netsh commands. Please check this article for additional information.
Please let me know if you have additional questions.
Thank you.
- Log in to post comments

It is'nt a great solution.....
1) Having VARIABLE-size data to copy, the delay-time setting may be too long as too short...
2) Backup and validation are run as separate tasks, but on same job... not on different job !
3) I suggest to add (for wish-list, if any..) a SEPARATE pre/post commands for "validation step",
for this or other purposes... a more flexible solution, I hope..
Tnx anyway, Anton
- Log in to post comments

Hello Sergio,
I am sorry for the inconvenience and you are most welcome.
I will also create an enhancement request and forward it to our Development team so that we can have the ability to use pre/post commands for validation.
If you need additional assistance, please let me know.
Thank you.
- Log in to post comments

Hi.
In ABR 11 Workstation this problem is back, but you can use 'Event tracing' ('Windows event log' in particular) as a workaround, because the event is generated AFTER the validation has ended. Just set it to 'Log the following event types: All events' for your backup plan (look in backup options) and then create a Windows scheduled task, with your post-backup commands, triggered by an 'On an event' trigger (you can do this on Vista or later).
Cheers,
mprost
- Log in to post comments