Cannot backup multiple files using acrocmd

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 1

So when I try to backup more than one file by name it doesn't work. I get the following error:

C:\Program Files (x86)\Acronis\CommandLineTool>acrocmd.exe backup file --include=E:\WSUS\WsusBackups\07Oct2013\07Oct2013Export.cab E:\WSUS\WsusBackups\07Oct2013\07Oct2013Export.log --loc=E:\ --arc=Sep2013Patches --backuptype=full --progress
Invalid command-line format.
Error: 0x1510001
$module = "acrocmd_vs_37687"
Tag: 0xB6053F4381056D4A
Parameter 'E:\WSUS\WsusBackups\07Oct2013\07Oct2013Export.log' is not recognized.
Error: 0x151004E
$module = "abr11cli_vs_37687"
Tag: 0x11154F871505E337

Documentation says:
Separators
A parameter name and a value list can be separated by either an equals sign or a space character. Values in a value list can be separated by either a comma or a space character.

Examples:
acrocmd backup disk --disk=1,2
acrocmd backup disk --disk=1 2
acrocmd backup disk --disk 1,2
acrocmd backup disk --disk 1 2

I've tried multiple ways of formatting it based on what the documentation says, all with the same result.

Can somebody help me out here? What am I missing?

Thanks for the help,

James

Tue, 10/08/2013 - 21:23
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 0
Comments: 1379

It should work but it doesn't. Use comma to separate items in parameters:
--include=E:\WSUS\WsusBackups\07Oct2013\07Oct2013Export.cab,E:\WSUS\WsusBackups\07Oct2013\07Oct2013Export.log

Wed, 10/09/2013 - 08:17
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 1

Thanks, that seemed to work...

I had actually tried that before, but I didn't realize the commas weren't translating correctly in Powershell. I Thought I'd tried it using an admin command prompt as well, but apparently not because it worked this time.

Is there no effort to correct the program or the documentation regarding this? I spent hours troubleshooting this. Could save some of my fellow scripters out there a lot time if one or the other were updated.

Thanks for the help,

James

Wed, 10/09/2013 - 15:28
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 0
Comments: 1379

To my best knowledge documentation is not corrected to reflect current behaviour if the behavior is incorrect. Nor have seen such a thing as errata sheet. The latest development build have this fixed, but these fixes most likely will be included only in the next major release.

Wed, 10/09/2013 - 17:54