Acronis B+R advanced Workstation 11 - pre-/post-command fails

Do I understand it right that you have a machine A that backs up some network shares lke \\machineB\someshare\ and wake that machineB in pre-command? It may simply have no time to wake up before actual backup plan starts executing, tries to access the shared folders, finds none and aborts.

What is the Pre-Command good for, if it will not do something BEFORE the backup on itself starts?
If the machine-B isn't online and the backup fails, all right. But the machine-B should be on the way waking up. If I test the comman with "Befehl testen", it works fine. I think it is a bug of the software. The description of the software says, that the Pre-Command will do something before the BACKUP itself. So what?
For additional info, the User has ALL permissions of an administrator.

If it ultimately wakes the machine you need to wait until it changes its state from "is on the way waking up" to "up and running all needed SMB services". You may insert a sleep command or some more sophisticated running 'ping' and 'errorlevel' until the machie wakes up and replies to pings.

Normaly you are right, but the other machine don't wake up. I have tried some things and found out why:

I created a backup of two file on my master-machine. As pre-command I set the wakup of the machine B. This works !.

So my result is, that acronis make a validation of the task and this fails, because it sees, that the data of the machine-B in my "backup-machine.-B-task" could not be reached. You will see this, if you have a task with a backup of data of an other machine and this machine is down. If you go to the definition of this task, you see that the software try to connect to the machine B. This is not possible. So I think, this is the reason, the task fails and no pre-command would be startet.

I think this is not correct, because the pre-command should be executed before the task-validation starts.

I am working on a work-around.

So my result is, that acronis make a validation of the task and this fails, because it sees, that the data of the machine-B in my "backup-machine.-B-task" could not be reached

It doesn't work this way. It doesn't touch the task data to before pre-command is completed. You may add something like time < nul >> some_log_file
to make sure the pre-command is launched. Or whether it isn't.

I disagree with "dev-non". It is a fact, that the pre-command "wake up machine B" not works, because the machine doesn't do any tweet. It is off!
If I backup local data with the same all other options, the pre-command wake up machine B. That's also a fact. I will try to write to a log-file, but the log-file of acronis couln't be correct.

Here is my Batch-file and logfile:
------------------------------------------------------------------
Echo.Start logging wakeup command >>D:\FocusBackupSettings\DE06wol_wake_logfile.txt
Echo.============================ >>D:\FocusBackupSettings\DE06wol_wake_logfile.txt
echo.%Date% >>D:\FocusBackupSettings\DE06wol_wake_logfile.txt
echo.%Time% >>D:\FocusBackupSettings\DE06wol_wake_logfile.txt

"C:\Program Files\WakeOnLANEx2\WOL2.exe" -wake "DE06.focusmr.co.de" -close

echo.RC= %errorlevel% >>D:\FocusBackupSettings\DE06wol_wake_logfile.txt
Echo.= executed sucessfull======= >>D:\FocusBackupSettings\DE06wol_wake_logfile.txt
---------------------------------------------------------------------------------------------------------------------------

Start logging wakeup command
============================
26.01.2012
9:32:40,64
RC= 0
= executed sucessfull=======

This is the result in a new file of the task, when the task backups local files. This works fine.
Now I deleted the log-file.

I started my task of backup machine B. The progessbar of the task still stand at 0% about 1 minute and after this I'll get following detail-information:

----------------------------------------------------------------------------------
ProtectCommand: Ausführen des Befehls fehlgeschlagen.
Zusätzliche Info:
--------------------
Fehlercode: 41
Module: 307
LineInfo: e6792a5ee190ddb3
Felder: $module : C:\Program Files (x86)\Acronis\BackupAndRecovery\mms.exe
Nachricht: ProtectCommand: Ausführen des Befehls fehlgeschlagen.
--------------------
Fehlercode: 29
Module: 307
LineInfo: d63b333701123474
Felder: $module : C:\Program Files (x86)\Acronis\BackupAndRecovery\mms.exe
Nachricht: LaunchBackupCommand: Ausführen des Befehls fehlgeschlagen.
--------------------
Fehlercode: 7
Module: 307
LineInfo: c37471ceffa18219
Felder:
Nachricht: Fehler bei Backup-Ausführung.
--------------------
Fehlercode: 52
Module: 307
LineInfo: a27873a62cd7bd33
Felder:
Nachricht: BackupPlanGenerator: Es ist ein Fehler bei der Erstellung eines zentralen Backup-Plans auf der Maschine aufgetreten (nach Deployment des Backup-Plans '913EED1E-2FCE-42FF-A15C-874A6B11AE69').
--------------------
Fehlercode: 15
Module: 331
LineInfo: a6005103f9d1691f
Felder:
Nachricht: GXT: Der 'Item Provider' hat ein Element nicht richtig aufgelöst, welches den Schlüssel '[PATH=data_required_item_uri&WORKGROUP=,mms::smb::data_required#4B2A7A93-A44F-4155-BDE3-A023C57C9431=gct::files]' hat. Grund für den Bericht: 'Route Enumeration' für '[PATH=data_required_item_uri&WORKGROUP=,mms::smb::data_required#4B2A7A93-A44F-4155-BDE3-A023C57C9431=gct::files]' starten.
--------------------
Fehlercode: 7
Module: 4
LineInfo: f35f747b3b21f994
Felder:
Nachricht: Fehler beim Öffnen der Datei.
-----------------------------------------------------------------------------------------

No logfile was created!. This are facts and couldn't be ignored.

Well, I tested it myself and you were right and I was not - it indeed tries to resolve the source and then fails without executing pre-backup command :( Even in case of a local backup plan.