Urbackupclientctl documentation

client
1

“urbackupclientctl status” gives me:

{
"capability_bits": 0,
"finished_processes": [],
"internet_connected": false,
"internet_status": "connected_local",
"last_backup_time": 0,
"running_processes": [],
"servers": [{
"internet_connection": false,
"name": "192.168.0.5"
}
],
"time_since_last_lan_connection": 41918
}

I need to change the address to “192.168.0.3”, since that is where the local server is. The one it’s currently connected to is outside the VM on the same machine. What’s the command to do this?

Also “urbackupclientctl --help set” helpfully tells me that I need to use “-k <setting key> -v <setting value>”, but I can’t actually find any documentation on what these settings might be. Can we have a nice list of keys and possible valid values please?

Thanks.

2

I resolved this by RTFM :wink:

3

But you are right. It needs some documentation, and an error if one specifies a non-existing setting and a get-settings command… and the status output should not be raw json per default… etc…

1 Like
4

Well I now have two servers, both working correctly, one backing up only files and the other backing up only images. I even managed to do this without losing the CBT status, despite shutting down clients and servers, and editing the idents.

The only small problem now is that, if both servers are active at the same time, the client favours the first server listed in the idents file, ignoring the other until the first server is shut down. This causes backups to be rejected if they are not of the type supported by the server’s settings (or potentially the wrong type of backup being sent to the wrong server, if I allow both types on both servers). So strictly speaking I cannot have more than one server running at the same time, at least not on the same subnet.

This is more of a feature request than a bug, since the client clearly hasn’t been designed to select which server to back up to, much less differentiate between backup destinations for different types of backups.

But still … it would be nice :slight_smile:

5

Oh, and while I’m on the subject of feature requests, how about a nice way of exporting the DSA keys to distribute to clients, and on the other side a nice way of importing them, so we don’t have to go through the process of shutting down clients and editing text files?

6

It seems I spoke too soon.

The setting “Connect to Internet backup server if connected to local backup server” solves that problem.