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.
Charlie54 :
Sep 11, 2019
Hello,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:Charlie54 :
Sep 11, 2019
I actually tried that before writting here...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.Charlie54 :
Sep 11, 2019
Hummm...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.Charlie54 :
Sep 11, 2019
I was so used to command lines where the program starts, executes the task, then quits...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.