UrBackup Server/Client 2.0.1 beta (with Mac OS X client)

Most of the changes are described in the blog:

The Linux command line interfaces have been redesigned since then as well.

This version now includes a Mac OS X client and a portable Linux client (for x86/x86_64/ARMv6/ARM64). I did not manage to get different OS X versions to run in Virtual Box. If anyone has pointers on how to do that in a comfortable and legal manner they would be appreciated.
The portable Linux client doesn’t have C+±exception support (yet). In my tests everything was functional but this is something that must be resolved before releasing a non-beta version.

Todo

  • Linux and Mac OS X client update is untested as of yet
  • UEFI/GPT testing
  • Update documentation
  • Server on FreeBSD is untested – probably won’t compile

Compatibility with prior versions

  • 2.x server with 1.4.x client full compatibility (please report issues)
  • 2.x client with 1.4.x server works only in local network mode (not via internet mode)
  • Older client/server combinations may work but were not tested
  • 1.x restore does not work with 2.x servers (improved login method)

Upgrade process

As always: Replace the executables and the database of the server/client will be updated on first running it. As always downgrading the database version after upgrading it is not possible, so you should backup the old database files especially since this is a beta.

Because of the improved file deduplication and statistics calculation the largest server table has to be completely rebuild. This may take a few hours depending on how many file entries you have. It will show the progress on the web interface but is not usable during the upgrade process.

Linux notes:

  • The wrapper scripts start_urbackup_server and start_urbackup_client have been removed. Please use the executable directly
  • The executable has been renamed to urbackupsrv (from urbackup_srv), the client to urbackupclientbackend (from urbackup_client)
  • There is a new command line interface for the client urbackupclientctl
  • All the plugins are now statically linked into one executable. This simplifies the compilation, debugging and packaging on Linux

Run the UrBackup server on Linux with e.g. urbackupsrv run --loglevel debug

Downloads

I just upgraded my test server and now can’t download the client. ERROR: Signature verification failed, I have deleted UrBackupUpdate.exe, UrBackupUpdate.sig and version.txt and restarted server

I was able to upgrade from 2.0 to 2.01 and all working fine.I was able to test the client in Ubuntu 14.10 and Windows 10 & 2012r2. So far no error.

@
Preprint_Computers although you get an error while trying to download the client from the web, if you download the client manually it all works fine.

Thank you for the new beta release

I’ve Upgraded to 2.0.1 busy with first backup. will report how things progress.

any idea when download of clients from web interface will work?

Hi,

Indeed it doesn’t compile on FreeBSD

Interface/Mutex.h:32:18: warning: no newline at end of file
In file included from Server.h:13,
from file_linux.cpp:26:
Interface/Condition.h:16:22: warning: no newline at end of file
In file included from Server.h:14,
from file_linux.cpp:26:
Interface/SharedMutex.h:35:3: warning: no newline at end of file
In file included from file_linux.cpp:28:
types.h:2:27: warning: no newline at end of file
file_linux.cpp: In member function ‘virtual bool File::PunchHole(_i64, _i64)’:
file_linux.cpp:320: error: ‘fallocate’ was not declared in this scope
*** [urbackupsrv-file_linux.o] Error code 1

Stop in /urbackup/urbackup-server-2.0.1.0.
*** [all-recursive] Error code 1

Stop in /urbackup/urbackup-server-2.0.1.0.
*** [all] Error code 1

Actually the client download (and update) should work at this time. I just noticed that some files are missing in the Windows installers causing this to fail with a Windows server. Will be fixed.

Hi Uroni,

Ok i have an issue where the server shows the client is indexing (its been 12hours) but the backup never gets going. both server and client are 2.0.1 beta windows

Server log hangs on this

16/02/02 20:42 INFO Starting incremental file backup…
16/02/02 20:42 DEBUG Holburn Server: Doing backup with hashes…
16/02/02 20:42 DEBUG Holburn Server: Doing backup with intra file diffs…
16/02/02 20:42 DEBUG Holburn Server: Connecting for filelist…
16/02/02 20:42 DEBUG Holburn Server: Waiting for filelist

Client debug log

2016-02-03 08:49:56: WARNING: SQLite: abort at 13 in [INSERT INTO files (name, tgroup, num, data) VALUES (?,?,?,?)]: UNIQUE constraint failed: files.name errorcode: 2067
2016-02-03 08:49:56: ERROR: Error in CQuery::Execute - UNIQUE constraint failed: files.name Stmt: [INSERT INTO files (name, tgroup, num, data) VALUES (?,?,?,?)]
2016-02-03 08:49:56: WARNING: SQLite: abort at 13 in [INSERT INTO files (name, tgroup, num, data) VALUES (?,?,?,?)]: UNIQUE constraint failed: files.name errorcode: 2067
2016-02-03 08:49:56: ERROR: Error in CQuery::Execute - UNIQUE constraint failed: files.name Stmt: [INSERT INTO files (name, tgroup, num, data) VALUES (?,?,?,?)]
2016-02-03 08:49:56: WARNING: SQLite: abort at 13 in [INSERT INTO files (name, tgroup, num, data) VALUES (?,?,?,?)]: UNIQUE constraint failed: files.name errorcode: 2067
2016-02-03 08:49:56: ERROR: Error in CQuery::Execute - UNIQUE constraint failed: files.name Stmt: [INSERT INTO files (name, tgroup, num, data) VALUES (?,?,?,?)]
2016-02-03 08:49:56: WARNING: SQLite: abort at 13 in [INSERT INTO files (name, tgroup, num, data) VALUES (?,?,?,?)]: UNIQUE constraint failed: files.name errorcode: 2067
2016-02-03 08:49:56: ERROR: Error in CQuery::Execute - UNIQUE constraint failed: files.name Stmt: [INSERT INTO files (name, tgroup, num, data) VALUES (?,?,?,?)]
2016-02-03 08:49:56: WARNING: SQLite: abort at 13 in [INSERT INTO files (name, tgroup, num, data) VALUES (?,?,?,?)]: UNIQUE constraint failed: files.name errorcode: 2067
2016-02-03 08:49:56: ERROR: Error in CQuery::Execute - UNIQUE constraint failed: files.name Stmt: [INSERT INTO files (name, tgroup, num, data) VALUES (?,?,?,?)]

This should be fixed with 2.0.2 now.