I am a new urbackup user. I have created a urbackup server on Windows Server 2022 machine and I have about 20 clients that I backup using Image only configuration and only over the internet, no local backups.
I am testing the debian based restore usb tool and I can connect to the server but I receive an error connecting to the service.
My attempts at enhancing debugging / logging to assist me in viewing exactly what is happening have failed.
Can anyone assist me with ideas on how to resolve this?
So if it’s supposedly connected, then why doesn’t it move onto the next step?
I’ve tried everything:
-swapping urbackup:// with the server IP
-tried using http & https:// with both the server IP and URL, both with and without the port 55414
I have no hair left on my head and my wife laughs at me! and then gives me the “L” sign.
I mean, this product just leaves you hanging!
I was going to create another thread, but I saw yours and figured I’d add to it.
I hope the developer or someone knowledgeable could help out here.
So I’m doing some more digging from some other posts while using the Linux client restore VM.
There is a directory /root that has some files that are dated from the restore attempt.
So:
-click on the bottom left goofy looking icon - select System Tools - LXTerminal
-this opens a CMD window (using Windows parlance )
-type sudo ls -l /root
-you should see a list of all the files with the date you attempted your restore
-the ones I’m looking at are:
restore_client.log
restore_http.log, and
restore_mode.txt
-for each, you can issue the following command to scan for “errors, or warnings”
-type sudo grep -iE ‘error|warn’ /root/OneOfTheAboveFiles.xxx | more
-or, sudo cat /root/OneOfTheAboveFiles.xxx | more to see all of the entries a screen at a time
this should list every entry that has ‘error or warning’ in it, you can cancel the list by hitting ‘q’
The noted messages I see from restore_client.log (for my situation) are:
Error: Error loading clouddriveplugin
next weird warning: AWS-CLient: SDK was built without http implementation…can’t create http client instance
then, ClientService cmd: STATUS DETAIL#pw=88cc…
followed by, rc=0 hasError=true state=0, which fills the log up
then at the end there’s - shutting down, shutting down plugins, and finally deleting server
From restore_http.log:
Error: Error loading clouddriveplugin
Error connecting to client service -1
From restore_mode.txt:
Error setting file permissions to “urbackup/data/settings.cfg”
IRONICALLY, it successfully connects to the urbackup://myurbackupxxxxx:55415
Go Figure!!
then a whole bunch of, ClientService cmd: STATUS DETAIL#pw=88cc…
Then it just craps off leaving me stuck at the Configure Server Connections window.
Yup! There she is again with the big “L” sign on her forehead
Thought of the day:
If you’re gonna backup without a proven means to restore, you’re FoRkEd!!
I figured out my problem, and it was a real face palm moment.
I changed the setting for “max active” clients to 10 during my initial configuration of the server. Thinking it would help QOS, well I have 20 clients so once I got debug enabled for logs I could see that I was connecting but timing out due to no slots available for my restore. Changed the setting to 50 and all is good.
You are connecting and if you can view you log it will tell you what’s happening.
I am using a windows 2022 server instance, no VM’s as my virtual knowledge is subpar.
You need to change the line in args.txt file to “debug” for logs, replacing “warn”. This one change has allowed me to not only solve my internet restore problem, it has allowed to me to resolve every single error I was receiving. My backup server is damn near perfect now.
