Thanks for testing @draga
I have rebuilt and reuploaded the source package and the debian package (with the same URL).
The Debian package is linked statically with crypto++ now to enable installation on more Debian variants and I probably built the static package wrong (for a previous gen Intel processor) + published the patched source distribution instead of the unmodified one.
Ok, I’ve started with the tests. I’ve compiled and run the server, and the first backup was ok. After some incremental ones, I’ve found the server had crashed with this error:
I tried to restart the server and the backups, after some time, were rescheduled. The server crashed again after some minutes, this time just with a segfault.
ok a couple of backups down and looks good. I’ve noticed better backup times with no indexing issues so far also the statistics issue I was having with negative backup sizes seems to be sorted but I will continue testing and revert with any issues.
Just a heads up, if you choose Swedish as language at logon (hurray we got Swedish) you get a blank screen with just the urbackup header and footer no username password fields (hurray Swedish?).
And if you logon as English and then change it to Swedish it stops working also.
The beta installers are not working correctly for xp machines. The install works properly then when it finishes the backup questionnaire opens under other windows, with an error message. The client states that it cannot connect to the server. If I install a 1.4.10 client work fine. Does 2.0 no longer support XP?
Yes this has already been confirmed windows xp is no longer supported with beta 2.0.x but you can still use an older client to connect to a 2.0.x server
Dear Mr. Uroni,
I have install the UrBackup Server 2.0.5 beta using the .deb file but few minutes after the server start I get the following error in the syslog and the process stop:
It’s still probably build wrong and uses SSE4 or something which your processor does not support. I’ll have another look at that with the next version.
Another issue I am seeing with 2.0.5beta is that a machine I just installed the client on is currently indexing, but the web interface does not show any activity for it. This is a local client, not over the internet. Client is Win10 Pro, server is 2012R2.