The parallel client-side file hashing is behind a feature flag in the internet settings tab on the server and needs to be enabled first.
Changes with server 2.2.5 beta
Updated translation
File backup with ZFS snapshots
Fix capa error return causing hung clients in rare cases
Fix client tokens/client authkey download
Ignore permissions if restoring from web interface without tokens
Add hint about network share access denied problem
Add option to send ok mails after fail mails
Narrow down trim range as far as possible after image backup in cow-raw mode
Don’t start file backups with the same group
Handle date case where localized day in date is shifted by one
Make inode_db envsize depend on free space during migration
Do not start metadata application before download is finished (fixes metadata application problems)
Delete symlink on file/image backup delete on ZFS
Do not run cleanup if backupfolder is not available
Fix rare race condition in file metadata download start
Disable deletion of last file backup from web interface (for now)
Major changes with server 2.2.x beta
Client-side file hashing parallel with file backup
Image backup restore via Internet client
Simultaneous file meta data application with file backups
Scriptable (lua) alerts and reports
File backup with ZFS snapshots
Changes with client 2.2.3 beta
Read 4K at a time for AF 4Kn disks in image backup
Skip data in metadata stream on Windows if file is sparse
Ignore unexpected error code in CBT return
Fix clientctl/GUI problem with long messages
Fix metadata reading from network shares on Windows
Set file owner before setting file permissions
Correctly handle file type changes during restore
Always use simple tokenize function (fixes issues with ‘"’ in settings)
Set block/char device major:minor correctly during restore
Major changes with client 2.2.x beta
Client-side file hashing parallel with file backup
Changes with Restore CD 2.1.x beta
Image backup restore via Internet client
Upgrade process
As always: Replace the executables (via the installers) and the database of the server/client will be updated on first running it.
Place the files from the update directory into C:\Program Files\UrBackupServer\urbackup or /var/urbackup to auto-update clients. Disable Download client from update server in the server settings to prevent the server from downloading the current version.
Stop the UrBackup server, restore C:\Program Files\UrBackupServer\urbackup or /var/urbackup from a backup before upgrade and then install the previous version over the beta release.
I think its got to do with the
ERROR: Signature verification failed
when trying to download the client from the web.
if i delete the Sig files and restart the urbackup service it doesn’t recreate these files and then the option of downloading the client from the portal is not available.
Thnx Uroni with the Sig files auto updates and download of client from web portal is working again. any reason why the web portal keeps showing incorrect IP address for clients as well as incorrect file backup status?
Could you post some details (e.g. what it shows as IP address and what would be the correct one…) as well as have a look at the log file if there are any errors?
auto update of clients… for macOS, they seem to update to 2.2.3 beta fine without issues (from 2.2.2 beta) … but when windows clients attempt to update, they lose connection and have to be removed and reinstalled. I’d like a way to update them on my own (without urbackup server, preferably installing over the top of the current AND keeping settings), but just running the installer when its already installed doesn’t work. The only method that seems to work for me is removing and reinstalling with the python script.
Similar experience here, automatically updating Windows client from 2.1.16 to 2.2.3 beta for Internet connected systems lost the Internet settings and thus connection. Most fields on Internet tab in Client settings were blank, including Internet server name/IP and server password. Fortunately I had already transitioned to group settings on the server so was able to download a pre-configured client, uninstall the empty one, and install the new, properly configured client.
As far as I can tell, the local systems updated successfully without manual intervention.
I’d like to test it, but “autoupdate clients” is a server setting, so it’d have to be turned on for all clients, which I don’t want to do and have to fix a bunch, which is another reason I’d rather just update them from alternative methods anyways, that way you can use a test group and manually push it when you feel like it, to just the clients you want.
ok so my setup is internet only clients to a windows server 2012 urbackup server and all their IP addresses are showing up as the gateway (of the servers local network) ip address in the web portal. also even though Incremental file backups are finishing without error since i upgraded from server 2.1.19 the status in the web portal shows as “No recent backup” even if a backup has just completed without error.