Unsolved

This post is more than 5 years old

1 Rookie

 • 

52 Posts

1486

November 9th, 2012 10:00

Error: One of the supplied parameters is invalid

I am trying to restore files from a test machine's VMImage backed up by Avamar.  Seems the task is getting scheduled, but soon after the restore started, it is failing.  Any idea what could be wrong in this syntax?  Here my source and target machines are same but the destination folder is different.  I have also created the folder priorly to see if that is the case though I think the destination folder will be created if it is not existing already.

root@avamar-01:~/#: mccli backup restore --name='/10.a.b.c/TestCustomers/Test-Venus/Venus-XP-21 (796ba339-a857-4509-828a-f8d60bd14cc8)' --labelNum=277 --plugin=3019 --restore-vm-to=flr --dest-client-domain='/10.a.b.c/TestCustomers/Test-Venus' --dest-client-name='Venus-XP-21 (796ba339-a857-4509-828a-f8d60bd14cc8)' --dest-client-username=Administrator --data=C:\\212 --dest-dir=C:\\415 --dest-client-password=XXXXXXX

0,22312,client restore scheduled.

Attribute   Value

----------- -----------------------------------------------------------------------------------------------------------------

client      /10.a.b.c/TestCustomers/Test-Venus/Venus-XP-21_796ba339-a857-4509-828a-f8_UCI2vHjpOTix6u9pMGy1OA

activity-id 9135248206100609

From log file:

Log #1: avvmwfile log 2012-11-09 17:25:33 UTC [6.1.100-402 Linux-x86_64]

2012-11-09 17:25:33 avvmwfile Info <5008>: Logging to /usr/local/avamarclient/var-proxy-1/MOD-1352481621942-bc6db286732e850ee83d026ffae9ac22a2ff226d-3019-vmwfilew.log

2012-11-09 17:25:33 avvmwfile Info <6673>: CTL listening on port 33870

2012-11-09 17:25:33 avvmwfile Info <10684>: Setting ctl message version to 3 (from 1)

2012-11-09 17:25:33 avvmwfile Info <16136>: Setting ctl max message size to 268435456

2012-11-09 17:25:39 avvmwfile Error <0000>: One of the supplied parameters is invalid

1 Message

May 28th, 2013 13:00


I'm sure the OP has found a solution, but others may be looking hard (I know I was). The drives/vmdk files are represented by a numerical number. In my environment the C drive is 1 and D drive is 2 etc.


So the --data parameter should read --data=1:\\Path\\To\\File instead of --data=C:\\Path\\To\|File.

No Events found!

Top