Non-negative return codes come from the main bvckup2.exe process, meaning that it got to see the command and responded to it:ġ00 through 106 => backup job status (see below)Ģ00 and 201 => licensing status (see below) 150 => timeout waiting for reply (30 sec)
110 through -130 => can't connect to the process 80 through -100 => can't find the process Negative return codes come from the "bvckup2.exe -command" process: Otherwise it will print a non-zero number, indicating a failure. Meaning "OK" if a job called "test backup" was in fact enabled. For example, if the following script is saved as command.bat:
#BVCKUP 2 CONFIGURATION WINDOWS#
If you are using a custom configuration folder, then you will need to pass its location using the -c argument:Ĭompletion status of a command is returned as a process exit code, which Windows puts in the %errorlevel% variable. This feature was introduced in Release 70 and several new commands were later added in R74.20 and R76. It is also possible to disable this feature completely.
It is possible to lock down the access so that only privileged accounts could access the app through this interface. The app can be controlled from the command line while it's running in both desktop or service mode. For example, it's possible to start a backup job, to check its status or to query whether the app has a valid license.
When Bvckup 2 is running, it is possible to control and query the app from command line.
0 kommentar(er)
