Ability to reconnect during indexing if connection is broken
Define which volumes need to be snapshotted together (snapshot groups)
Image backup mounting, browsing and archival on Windows, Linux and FreeBSD (does not work in FreeBSD jails and with VHD/VHDZ on FreeBSD)
Major changes with client 2.1.x beta
Ability to reconnect during indexing if connection is broken
Improved image backup performance
Windows Backup API support (tested backup and restore with Microsoft SQL, tested backup with Microsoft Exchange and Hyper V)
File backups and restores use the change block data from the change block tracking driver now (you can install the beta client over a CBT client and this will work)
Define which volumes need to be snapshotted together (snapshot groups)
Changes with server 2.1.8 beta
Refcount image mounted lock to allow multiple locks
Correctly reset background thread priority on Windows
Fix: Do not set images in snapshot group to complete until the whole finishes
Manual deletion of file and image backup from web interface
Refactor data classes to fix bug
Per backup temporary file folders
Interpret “-1” as throttling being disabled again (for compatibility reasons)
Fix: Display correct archive type
Ignore group setting for default group
Handle send failure in file client gracefully and not by accidentally queuing two same chunks
Only start scheduled backup if client is online
Skip initial WAL checkpoint for faster startup
Changes with client 2.1.8 beta
Correctly reset background thread priority on Windows
Add start tokens to additionally created volumes in group so that they do not get prematurely deleted
Enumerate domain user accounts and groups
Send info about users with local profile to server
Increase idle timeout to 5min after indexing
LDAP/AD login: Make username case insensitive
Launch browser via jump file if URL is too long
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.
Just upgrade my test server (the ZFS one), made a backup test and it’s looks like all is OK.
However, with future versions , it should be nice to detect automatically if ZFS is used and then set-up “-u root” automatically in /etc/init.d/urbackupsrv :
Maybe adding a new parameter in /etc/default/urbackup will be simplier (e.g RUN_AS_ROOT=1 or DAEMON_USER=root) and adding a test in /etc/init.d/urbackup to launch as root or not.
Or something like this …
BTW, could you officialize the HTTP_PROXY parameter in this file ?
Got a segmentation fault when marking image backups for deletion and then running in CLI “urbackupsrv remove-unknown” or “urbackupsrv cleanup”. On the other hand, “Delete now” from GUI works fine.
root@svurbackup:~# urbackupsrv remove-unknown
2016-12-23 14:55:16: Going to remove all unknown files and directories in the urbackup storage directory. Waiting 20 seconds...
2016-12-23 14:55:36: Shutting down all database instances...
2016-12-23 14:55:36: Opening urbackup server database...
2016-12-23 14:55:36: Testing if backup destination can handle subvolumes and snapshots...
Testing for btrfs...
Create subvolume '/media/urbackup/testA54hj5luZtlorr494/A'
Create a snapshot of '/media/urbackup/testA54hj5luZtlorr494/A' in '/media/urbackup/testA54hj5luZtlorr494/B'
Delete subvolume (commit): '/media/urbackup/testA54hj5luZtlorr494/A'
Delete subvolume (commit): '/media/urbackup/testA54hj5luZtlorr494/B'
BTRFS TEST OK
2016-12-23 14:55:36: Backup destination does handle subvolumes and snapshots. Snapshots enabled for image and file backups.
2016-12-23 14:55:36: Cleaning up 0 percent
2016-12-23 14:55:36: Cleaning up 0 bytes on backup storage
2016-12-23 14:55:36: Database cache size is 200 MB
2016-12-23 14:55:36: Starting cleanup...
2016-12-23 14:55:36: Freeing database connections...
Erreur de segmentation
root@svurbackup:~#
dmesg shows :
[1895585.474828] free space[21993]: segfault at 8 ip 00000000009da060 sp 00007f4b617f9818 error 4 in urbackupsrv[400000+898000]
root@svurbackup:~# export LANG=en_EN.UTF8 ; gdb --args urbackupsrv remove-unknown
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from urbackupsrv...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/urbackupsrv remove-unknown
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff29cb700 (LWP 23131)]
2016-12-23 15:20:20: Going to remove all unknown files and directories in the urbackup storage directory. Waiting 20 seconds...
2016-12-23 15:20:40: Shutting down all database instances...
2016-12-23 15:20:40: Opening urbackup server database...
[New Thread 0x7ffff1ec9700 (LWP 23160)]
[New Thread 0x7ffff16c8700 (LWP 23161)]
[New Thread 0x7ffff0ec7700 (LWP 23162)]
[New Thread 0x7fffe3fff700 (LWP 23163)]
[New Thread 0x7fffe37fe700 (LWP 23164)]
[New Thread 0x7fffe2ffd700 (LWP 23165)]
2016-12-23 15:20:40: Testing if backup destination can handle subvolumes and snapshots...
Testing for btrfs...
Create subvolume '/media/urbackup/testA54hj5luZtlorr494/A'
Create a snapshot of '/media/urbackup/testA54hj5luZtlorr494/A' in '/media/urbackup/testA54hj5luZtlorr494/B'
Delete subvolume (commit): '/media/urbackup/testA54hj5luZtlorr494/A'
Delete subvolume (commit): '/media/urbackup/testA54hj5luZtlorr494/B'
BTRFS TEST OK
2016-12-23 15:20:41: Backup destination does handle subvolumes and snapshots. Snapshots enabled for image and file backups.
2016-12-23 15:20:41: Cleaning up 0 percent
2016-12-23 15:20:41: Cleaning up 0 bytes on backup storage
2016-12-23 15:20:41: Database cache size is 200 MB
2016-12-23 15:20:41: Starting cleanup...
2016-12-23 15:20:41: Freeing database connections...
[New Thread 0x7fffe27fc700 (LWP 23185)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe27fc700 (LWP 23185)]
0x00000000009da060 in ?? ()
(gdb) bt
#0 0x00000000009da060 in ?? ()
#1 0x000000000040aeb3 in ?? ()
#2 0x0000000000667fc2 in ?? ()
#3 0x00000000006616ca in ?? ()
#4 0x000000000065e1e9 in ?? ()
#5 0x000000000047dd5c in ?? ()
#6 0x0000000000429ef5 in ?? ()
#7 0x00007ffff6ddf0a4 in start_thread (arg=0x7fffe27fc700) at pthread_create.c:309
#8 0x00007ffff6b1462d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
(gdb)
How can we fix this please ? Because now it doesn’t remove old backups and free space on the server decreases.
It looks like table clients_hist from backup_server.db isn’t updating since few days :
Also, I can’t access backups via web GUI anymore, clicking on the computer name doesn’t do anything, selecting “Access/Restore backups” in the clients brings me to an empty UrBackup page.
In the meantime i’ve started to clean manually from GUI to keep only the 5 last incremental, except for client ID=22 and ID=23 which still have 8 incremental (instead of 5 = “Maximal number of incremental image backups”).
Here’s the cleanup outpout :
root@backup-2:~# urbackupsrv cleanup -a 50%
2016-12-28 15:29:38: Shutting down all database instances...
2016-12-28 15:29:38: Opening urbackup server database...
2016-12-28 15:29:38: Testing if backup destination can handle subvolumes and snapshots...
Testing for btrfs...
Create subvolume '/media/c4d5fd17-2c8b-493b-8f6b-af8514c2e941/backups/testA54hj5luZtlorr494/A'
Create a snapshot of '/media/c4d5fd17-2c8b-493b-8f6b-af8514c2e941/backups/testA54hj5luZtlorr494/A' in '/media/c4d5fd17-2c8b-493b-8f6b-af8514c2e941/backups/testA54hj5luZtlorr494/B'
Delete subvolume (commit): '/media/c4d5fd17-2c8b-493b-8f6b-af8514c2e941/backups/testA54hj5luZtlorr494/A'
Delete subvolume (commit): '/media/c4d5fd17-2c8b-493b-8f6b-af8514c2e941/backups/testA54hj5luZtlorr494/B'
BTRFS TEST OK
2016-12-28 15:30:08: Backup destination does handle subvolumes and snapshots. Snapshots enabled for image and file backups.
2016-12-28 15:30:08: Cleaning up 50 percent
2016-12-28 15:30:08: Cleaning up 2.71797 TB on backup storage
2016-12-28 15:30:08: Database cache size is 200 MB
2016-12-28 15:30:08: Starting cleanup...
2016-12-28 15:30:08: Freeing database connections...
2016-12-28 15:30:08: Space to free: 2.71797 TB
2016-12-28 15:30:08: Enough free space now.
2016-12-28 15:30:08: Enough free space now.
2016-12-28 15:30:08: Client with id=22 has 4 full image backups max=26
2016-12-28 15:30:08: Client with id=22 has 3 incremental image backups max=5
2016-12-28 15:30:08: Client with id=18 has 4 full image backups max=26
2016-12-28 15:30:08: Client with id=18 has 3 incremental image backups max=5
2016-12-28 15:30:08: Client with id=20 has 4 full image backups max=26
2016-12-28 15:30:08: Client with id=20 has 3 incremental image backups max=5
2016-12-28 15:30:08: Client with id=23 has 4 full image backups max=26
2016-12-28 15:30:08: Client with id=23 has 3 incremental image backups max=5
2016-12-28 15:30:08: Client with id=19 has 4 full image backups max=26
2016-12-28 15:30:08: Client with id=19 has 3 incremental image backups max=5
2016-12-28 15:30:08: Client with id=21 has 4 full image backups max=26
2016-12-28 15:30:08: Client with id=21 has 3 incremental image backups max=5
2016-12-28 15:30:08: Deleting old logs...
2016-12-28 15:30:08: Done deleting old logs
2016-12-28 15:30:08: Cleaning history...
2016-12-28 15:30:08: Rewriting daily history...
2016-12-28 15:30:08: Reading history...
2016-12-28 15:30:08: 276 history items read
2016-12-28 15:30:08: Deleting history...
2016-12-28 15:30:08: Writing history...
2016-12-28 15:30:09: Rewriting monthly history...
2016-12-28 15:30:09: Reading history...
2016-12-28 15:30:09: 0 history items read
2016-12-28 15:30:09: Deleting history...
2016-12-28 15:30:09: Writing history...
2016-12-28 15:30:09: Rewriting yearly history...
2016-12-28 15:30:09: Reading history...
2016-12-28 15:30:09: 0 history items read
2016-12-28 15:30:09: Deleting history...
2016-12-28 15:30:09: Writing history...
2016-12-28 15:30:09: Done cleaning history
2016-12-28 15:30:09: Cleaning deleted backups history...
2016-12-28 15:30:09: Done cleaning deleted backups history.
2016-12-28 15:30:09: Cleaning up client lists...
2016-12-28 15:30:09: Done cleaning up client lists.
2016-12-28 15:30:09: Updating statistics...
2016-12-28 15:30:09: Updating image stats...
2016-12-28 15:30:13: Updating file statistics...
2016-12-28 15:30:13: Done updating statistics.
2016-12-28 15:30:13: Enough free space now.
2016-12-28 15:30:14: Cleanup successfull.
root@backup-2:~#
Yes i know that.
E.g, client ID=22 have 7 full image backups (2 of which are archived) and 8 incremental backups.
But cleanup only see 4 full (instead of 7-2=5) and 3 incr (instead of 8) …
Ok thanks this is done, few rows have been updated from NULL to 0.
However, “Last image backup” field in the Status tab is still not up to date, how can we refresh this ?
Maybe on next backup ? Restarting the server doesn’t help …
I’ve made a new backup but it doesn’t update the last image backup field …
I’m afraid that on the next cleanup the server deletes all recent backups (> 22/12).
