Here as requested (just take the screenshots): working and not working clients, respectively.
EDIT: just complementing; the first one is a Ubuntu 16.04; the second (not working), is a Debian 6, but I guess this isn’t the problem either. There are Debian 6 clients that are working; also, there are working and not working CentOS 6 clients. Hard to urderstand for now, but trying to.
After a batch of restarts (both, server and problematic clients), it ended up running, finally. Couldn’t understand yet this “exact” science of ours, but, well, finally worked.
Thank you very much for you all, specially uroni and Jejanim.
Make sure the server thinks it’s online before you try doing a restore.
You’re probably using this because:
old machine was backed up
You install new machine
Download client for old machine and install it
Want to push a restore of the files from old machine to new machine.
Archive your snapshot so it doesn’t get cleaned before you’re finished
Run a new backup with “Default directories to backup” to a newly created folder eg c:\temp\
Check to make sure Online = Yes
Then try and do the restore of the files from the previous machine/backup, see if the button is there.
@uroni It would be nice to have a diagnostic view into what’s connected/how/methods for troubleshooting. I think I’ve finally gotten the hang of it and how to try and get it into Online mode, but it’s not obvious when starting out.
I have the same issue (the restore button missing).
Some oldest servers are working fine, but the last installed has the pb, with the same configuration than the others.
The server status is online and backup are working.
It is an old topic, so I wonder if somebody find a solution on this ?
Per screenshot, is the CLIENT reading as online = Yes in the status page?
Wait until it does (which can take 5-10mins - keep switching screens Activities/Status) before attempting the restore. Until client reads as online you will not get the restore button
I had a similar issue (button present for some clients but not others). RESTORE=“server-confirms” helped but a reboot of the client and a restart of the server’s service weren’t enough. It worked only after I rebooted the server.
I came across Urbackup due to an evaluation of open source tools; while searching for a restore button I came across this discussion and like to add (if not already mentioned) …
Ubuntu 18.04, client version 2.4.11, server version 2.4.19 (running as docker container)
Changed /etc/default/urbackupclient option RESTORE from disabled to “server-confirms” (with quotes) and did a systemctl restart urbackupclientbackend.service …
no success, no restore button
… did a new full backup of the client and had a look for the appearance of the button …
no success, no restore button
… deleted old backups, adjusted settings for incrementell and full backups, did a full backup and …
no success, no restore button
… restarted the docker container …
no success, no restore button
… restarted the client with a time delay between start and stop of 300 seconds …
success, restore button is showing up.
This leaves me a bit unsure about Urbackup and its reliability. But anyway I will give it a try.
Same problem with linux clients (can’t say about Win ones, I have none yet since I 'm still evaluating urbackup).
I just wanted to confirm this behavior on Ubuntu 20.04 (both client and server). The rest of problems I had with this software keeps me from trying further.