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).
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.
Changes with server 2.0.7 beta
Fixed scheduling bug which caused it to run full backups all the time
Properly modify change indicator if full file backup is interrupted for correct folder metadata download
Changes since last version
Further optimized file backup deletion
Optimized full file backup indexing on client side
Don’t update local backup success status on unsuccessfull or image backup without shadowcopy (SYSVOL)
Open files differently during indexing such that some on-access virus scanners do not scan them (speeds up indexing significantly)
Fixed adding/removing backup paths via command line
Correctly log full file backup if started by incremental file backup
Fixed assertion failure during indexing
Fix issues with tar content backup
Keep track of shares in use and delay snapshot removal if necessary
Fixed Linux & Mac OS X client update
Fixed and documented time specific backup intervals and speed limits
Correctly show changed settings on Linux and Mac OS X client GUI frontend
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
I just upgraded a test server to 2.0.6 beta and downloaded the client from the web interface for the desktop that I am using for a test and I get this error:
ERROR: No server public key. Server version probably not new enough.
2016-03-23 15:18:57: ERROR: No server public key. Server version probably not new enough.
2016-03-23 15:26:05: ERROR: No server public key. Server version probably not new enough.
2016-03-23 15:26:05: ERROR: No server public key. Server version probably not new enough.
Fresh installation Debian 8 with backport kernel + btrfs 15TB storage om HP Micro server.
Installation was succes, and now running first full File backup, from 2 x Linux nas + 1 Win 7 client. Will add More clients soon.
Under installation in a Linux client om pretty sure i selected No snapshots.
But now I get this error:
Errors
24/03/16 10:45
Creating snapshot of “printjobs” failed.
Errors
24/03/16 10:45
Creating snapshot of “fælles” failed.
Disregard. The error was all my own doing. I had a separate UrBackup instance running on that machine that I had not completely disabled. Disabled it, rebooted, all is right in the world. Apologies for the confusion @uroni.
I can confirm that my testing server is also running image backups over and over again. My office desktop has run six full image backups since deploying 2.0.6 beta.
Server is running on 2012R2 and the client in question is Win10 Pro. Also, it is even more odd as I have full image backups turned completely off right now.
Actually, looking over recent activities, no incrementals have run. It has been a string of full file backups followed by full image backups for the clients that have been on this server and have been on. My laptops have done no incrementals either. My iMac has run 4 full file backups in 2 days. My desktop in my office has run 5 (correction from earlier, I miscounted) full image backups but has not run a file backup at all.
No worries. We are testing things to help make the software better. Nothing critical. Do what you can, when you can.
If it helps any, I did see one file backup from a Windows machine. It is a new laptop that I just added to the test environment last night. It ran a full file backup, and is not stuck in the image backup loop.
You work quickly. Does the 2.0.6 beta client still calculate file hashes twice? I have a couple of clients that I would like to test that back up over the internet, but the double calculation causes the backup to never start. The last time I tried, it was stuck on calculating file hashes for 4 days before I stopped.
Could you have look at the log file, if it has written out a crash dump? If yes I would be interested in that.This sometimes does not seem to work. Then you’d need to setup dump collection and wait for another crash: https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181(v=vs.85).aspx (Full dump preferred).
Also of interest would be the file it crashes on. For example if it is sparse (or contains zeroed areas) or if you are transferring it with the chunk hashes transfer method.
This the server log before it crashed around 01:49
WARNING: Entry from file entry index not found. File entry index probably out of sync. Needs to be regenerated. (id=1634948)
2016-03-26 00:40:26: ERROR: Connection broken: Removing shadow copy on “Home-PC” for path “Stuff” failed
2016-03-26 00:47:27: WARNING: Entry from file entry index not found. File entry index probably out of sync. Needs to be regenerated. (id=1634959)
2016-03-26 00:54:35: WARNING: Entry from file entry index not found. File entry index probably out of sync. Needs to be regenerated. (id=1634968)
2016-03-26 01:04:30: WARNING: Entry from file entry index not found. File entry index probably out of sync. Needs to be regenerated. (id=1634979)
2016-03-26 01:10:26: ERROR: Connection broken: Activating shadow copy on “Home-PC” for path “Documents” failed
2016-03-26 01:49:28: ERROR: Chunk not requested. (47710208)
2016-03-26 01:49:28: ERROR: Pending chunk: 1048576
2016-03-26 01:49:28: ERROR: Pending chunk: 1572864
2016-03-26 01:49:28: ERROR: Pending chunk: 2097152
2016-03-26 01:49:28: ERROR: Pending chunk: 2621440
2016-03-26 01:49:28: ERROR: Pending chunk: 3145728
2016-03-26 01:49:28: ERROR: Pending chunk: 3670016
2016-03-26 01:49:28: ERROR: Pending chunk: 4194304
2016-03-26
