Acrocmd --log not showing progress
Using the acrocmd replicate command, I'm pushing backups to an external drive and emailing the log file to verify completion. Things are quickly and easily visible in my 11.5 installations, because the .xml files are relatively large due to the progress indicator being included.
My 11.7 installation log files are not going beyond 2KB because progress is not logged. I've updated to the April 15th release, no change.
I've tried with and without the --progress switch, no difference. Is it me or is this no longer functioning?
Progress header from the 11.7 log file:
<progress_info>
<progress>0
</progress>
<elapsed_time>00:00:00
</elapsed_time>
<estimated_time>00:00:00
</estimated_time>
</progress_info>
<total_time>01:06:06
</total_time>
</output_data>
</replicate_backup>
Here's the content of my batch file with identifying information removed:
rmdir /S /Q E:\DC1\
rmdir /S /Q E:\App\
mkdir E:\DC1\
mkdir E:\App\
del D:\LOGS\DC1.xml
del D:\LOGS\App.xml
acrocmd replicate backup --loc=bsp://[StorageNode]/[VaultName] --credentials=[redacted] --arc=DC1_Archive(1) --Target=E:\DCI\ --progress --log=D:\Logs\DC1.xml
acrocmd replicate backup --loc=bsp://[StorageNode]/VaultName] --credentials=[redacted] --arc=App_Archive(1) --Target=E:\App\ --progress --log=D:\Logs\App.xml
2 logs attached; DC1-117.xml is the direct log from the batch above, MAIL-115.xml is what I want, from a working 11.5 installation using the same [modified for the installation names] batch process.
By the way, why do you need progress information to be included in the log file? Do you calculate average speed or something?
I can't find a better way of outputting the job status from an acrocmd run. If the log file is expected to be 256KB on a successful run from the progress log, then I can glean that from the file size, delete it and move on; whereas if it's far under the expected size, I know to check it for an error.
We will check this issue in our test lab.
IF %ERRORLEVEL% NEQ 0To check job status from acrocmd you can use "IF %ERRORLEVEL% NEQ 0if %errorlevel% neq 0 goto errorLabel".
For example:
acrocmd replicate backup ...
IF %ERRORLEVEL% NEQ 0if %errorlevel% neq 0 goto errorLabel
echo Job status is OK
exit
:errorLabel
echo Job status is Error
Your suggestion will work for the most part.
acrocmd won't trigger an error if the source archive isn't found or the provided credentials don't work, otherwise it is fine and I would consider this resolved. Thanks for the lesson.
By the way, we reproduced the issue and it will be fixed in future updates to 11.7.