1

Alex Pankratov :

Sep 11, 2019

This is covered in https://bvckup2.com/support/forum/topic/411, you just pass your config path using -c after --command:

    bvckup2.exe --command -c <your-config-path> start *

This will start all jobs.

2

Charlie54 :

Sep 11, 2019

thanks !

3

Charlie54 :

Sep 11, 2019

I actually tried that before writting here...

But it doesnt do anything... I excpected a display of a progress of somekind but nothing happens.

Also, when I open the main interface, the backup jobs haven't updated

4

Alex Pankratov :

Sep 11, 2019

There's no on-screen output. The result is communicated through the exit code. Check it and go from there. See the post I linked to above for details.

6

Charlie54 :

Sep 11, 2019

Hummm...

Your program handles commandline in a new way for me...

I think I first need to RUN it...

Wait a little bit...

THEN, issue another command line to run the jobs...

It doesn't work when I put all commands in the same line...

So this DOES NOT WORK...

bvckup2.exe --command -c Custompath start *

this DOES WORK

bvckup2.exe -c Custompath
Wait a little bit then
bvckup2.exe --command -c Custompath start *

7

Charlie54 :

Sep 11, 2019

I think Bamit ran into a similar

8

Alex Pankratov :

Sep 11, 2019

Well, yes, it's a command-line _control_ of an already running instance. The principal bvckup2 process needs to be up and running. Once it's up, you can then send it a command to do this or that.

9

Charlie54 :

Sep 11, 2019

I was so used to command lines where the program starts, executes the task, then quits...

This is different than anything I have worked with...

You are unique. :)

10

Alex Pankratov :

Sep 11, 2019

I can assure that this is very far from being unique, especially in a domain of always-on services. It's one of the most common forms of scriptable external control.