UrBackup Server 2.0.25 beta/Client 2.0.21 beta

uroni · June 2, 2016, 11:21am

The major changes are described in the blog: http://blog.urbackup.org/223/new-in-urbackup-2-0-x

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.25 beta

Corrected file path where update location is read from
Allow different versions for the different OS clients
More consistent backup running accounting
Only warn if file cannot be opened and if backing up without snapshot
Create image snapshot before connecting to client
Lower reconnection timeout if shutting down file client
Gracefully handle case where symlinking data directory succeeds and symlinking metadata directory fails
Allow configuration of SQLite mmap on Linux/FreeBSD
Sync backup storage file system before marking file backup as complete

Changes with client 2.0.21 beta

Handle pkg-config not being installed in Linux installer
Allow different versions for the different OS clients
Use posgres user for pg_dumpall (Linux client)
Improve read error handling in chunked sending
Improve modified directory cache invalidation before file backups

Todo

UEFI/GPT testing

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 (via the installers) 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 de-duplication 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

Server: https://limitingfactor.urbackup.org/Server/2.0.25%20beta/
Client: https://limitingfactor.urbackup.org/Client/2.0.21%20beta/
Restore: https://limitingfactor.urbackup.org/Restore/2.0.1/ (not updated)
WIP admin manual: admin_guide.pdf (368.5 KB) (not updated)

TomTomGo · June 2, 2016, 4:11pm

For information, full backup image failed after upgrading server to 2.0.25 and client to 2.0.21 (autoupdate from the server) with error :

Report:
( 3 infos, 0 warnings, 3 errors )

2016-06-02 18:04:46(info): Starting full image backup...
2016-06-02 18:04:48(info): Basing image backup on last incremental or full image backup
2016-06-02 18:04:48(error): Could not read MBR
2016-06-02 18:04:48(error): Cannot retrieve master boot record (MBR) for the disk from the client.
2016-06-02 18:04:48(info): Time taken for backing up client SV201: 2s
2016-06-02 18:04:48(error): Backup failed

Restarting the UrBackup service on the client fix the problem.

Regards,

AETCO · June 2, 2016, 6:56pm

Oops… I think I found a bug / have a feature request.

One of my windows users was able to right-click on the UrBackup client (version 2.0.20) in the system tray and selected “Accss/restore backups”. The user who was unfamiliar with the way UrBackup works, simply hit the restore button on the first page shown (basically restoring his entire C:\ drive from an earlier backup); thus erasing his current work for the last few hours

I also noticed that if a windows user reboots and then right-clicks on the client icon in the system tray before the client connects to the server, the options are not restricted to what I set on the server. The options are the default (allow most). I’m not sure if they will be allowed to change settings, but they can see the options until the client connects to the server.

I would like to see an option in the server settings (permissions tab) that can block the users from restoring files. (to avoid the accidental overwriting of files). Please remember that some users are barely able to turn a computer on; they certainly are not expert in matters of file systems and consequences of overwriting files. If possible, it might also be more consistent for the client to store the last server permission restrictions so the client can only see the permitted options on the next reboot.

In case you don’t hear it enough: Excellent software, Thank you!

Manley23 · June 2, 2016, 10:52pm

The 2.0.25 server MSI installed like normal and overwrote the 2.0.24 files. But the 2.0.21 client would not over-write in Windows. I got a big window pop-up saying I had to uninstall UrBackup client before installing new client version. It never did that before. So, I uninstalled 2.0.20 client and then installed 2.0.21 and it worked like normal.

TomTomGo · June 3, 2016, 11:20am

On cleanup phase today i was having WARNINGS in urbackup.log :

2016-06-03 12:11:53: ERROR: LMDB: Failed to delete data (MDB_NOTFOUND: No matching key/data pair found)
2016-06-03 12:12:00: WARNING: File entry with id 101070434 with filesize 1849 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101070443 with filesize 885 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101070446 with filesize 937 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101070460 with filesize 1054 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101070518 with filesize 1866 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101070520 with filesize 877 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101070521 with filesize 936 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101070523 with filesize 1049 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101070547 with filesize 1877 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101070555 with filesize 887 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101070556 with filesize 941 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101070558 with filesize 1049 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101071435 with filesize 1879 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101071436 with filesize 864 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101071438 with filesize 942 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101071439 with filesize 1040 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101071443 with filesize 1874 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101071551 with filesize 863 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101071553 with filesize 939 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101071554 with filesize 1046 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101071784 with filesize 1870 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101071786 with filesize 886 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101071787 with filesize 940 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101071792 with filesize 1047 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101071793 with filesize 1870 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101071797 with filesize 885 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101071798 with filesize 940 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101071799 with filesize 1047 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101072066 with filesize 1882 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101072075 with filesize 880 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101072076 with filesize 941 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101072077 with filesize 1048 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101072223 with filesize 1878 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101072224 with filesize 890 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101072225 with filesize 941 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101072226 with filesize 1042 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101073190 with filesize 1873 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101073194 with filesize 879 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101073426 with filesize 941 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101073428 with filesize 1050 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101073827 with filesize 1874 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:00: WARNING: File entry with id 101073831 with filesize 882 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:01: WARNING: File entry with id 101074066 with filesize 939 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:01: WARNING: File entry with id 101074067 with filesize 1044 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:01: WARNING: File entry with id 101074068 with filesize 1872 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:01: WARNING: File entry with id 101074069 with filesize 876 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:01: WARNING: File entry with id 101074070 with filesize 941 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:01: WARNING: File entry with id 101074071 with filesize 1049 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:01: WARNING: File entry with id 101074150 with filesize 1877 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:01: WARNING: File entry with id 101074153 with filesize 941 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:01: WARNING: File entry with id 101074202 with filesize 1853 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:01: WARNING: File entry with id 101074203 with filesize 880 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:01: WARNING: File entry with id 101074206 with filesize 941 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:01: WARNING: File entry with id 101074208 with filesize 1051 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:01: WARNING: File entry with id 101074209 with filesize 1853 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:01: WARNING: File entry with id 101074210 with filesize 880 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:01: WARNING: File entry with id 101074211 with filesize 941 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:01: WARNING: File entry with id 101074212 with filesize 1051 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:19: WARNING: File entry with id 101056891 with filesize 1888 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:19: WARNING: File entry with id 101056892 with filesize 866 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:19: WARNING: File entry with id 101056893 with filesize 940 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:19: WARNING: File entry with id 101056894 with filesize 1049 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:19: WARNING: File entry with id 101056895 with filesize 1888 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:19: WARNING: File entry with id 101056896 with filesize 865 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:19: WARNING: File entry with id 101056897 with filesize 940 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:19: WARNING: File entry with id 101056904 with filesize 1049 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:19: WARNING: File entry with id 101056905 with filesize 1879 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:19: WARNING: File entry with id 101056946 with filesize 864 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:19: WARNING: File entry with id 101056947 with filesize 940 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:19: WARNING: File entry with id 101056955 with filesize 1043 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:19: WARNING: File entry with id 101056958 with filesize 1890 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:19: WARNING: File entry with id 101056959 with filesize 878 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:19: WARNING: File entry with id 101056960 with filesize 939 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:19: WARNING: File entry with id 101056961 with filesize 1057 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:32: WARNING: File entry with id 101107722 with filesize 489 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:39: WARNING: File entry with id 101206230 with filesize 1891 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:39: WARNING: File entry with id 101206273 with filesize 883 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:39: WARNING: File entry with id 101206276 with filesize 940 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:39: WARNING: File entry with id 101206286 with filesize 1056 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:39: WARNING: File entry with id 101206295 with filesize 1891 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:39: WARNING: File entry with id 101206377 with filesize 884 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:39: WARNING: File entry with id 101206446 with filesize 940 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:39: WARNING: File entry with id 101206447 with filesize 1056 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207106 with filesize 1875 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207107 with filesize 848 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207109 with filesize 939 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207110 with filesize 1047 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207305 with filesize 1875 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207306 with filesize 870 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207387 with filesize 940 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207388 with filesize 1054 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207389 with filesize 1875 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207390 with filesize 871 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207391 with filesize 940 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207392 with filesize 1054 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207393 with filesize 1871 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207394 with filesize 893 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207395 with filesize 939 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207396 with filesize 1053 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207397 with filesize 1871 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207398 with filesize 895 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207399 with filesize 939 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207400 with filesize 1053 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207402 with filesize 1861 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207403 with filesize 940 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207404 with filesize 1044 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207451 with filesize 1861 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207453 with filesize 940 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207454 with filesize 1044 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207455 with filesize 1899 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207456 with filesize 938 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207458 with filesize 1039 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:40: WARNING: File entry with id 101207459 with filesize 769 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:53: WARNING: File entry with id 100919808 with filesize 1867 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:53: WARNING: File entry with id 100919810 with filesize 876 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:53: WARNING: File entry with id 100919812 with filesize 936 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:53: WARNING: File entry with id 100919826 with filesize 1049 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:53: WARNING: File entry with id 100919829 with filesize 1867 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:53: WARNING: File entry with id 100919831 with filesize 876 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:53: WARNING: File entry with id 100919841 with filesize 936 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:12:53: WARNING: File entry with id 100919842 with filesize 1049 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:13:01: ERROR: LMDB: Failed to delete data (MDB_NOTFOUND: No matching key/data pair found)
2016-06-03 12:13:33: WARNING: File entry with id 101206310 with filesize 1875 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:13:33: WARNING: File entry with id 101206311 with filesize 894 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:13:33: WARNING: File entry with id 101206312 with filesize 934 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:13:33: WARNING: File entry with id 101206313 with filesize 1038 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:13:33: WARNING: File entry with id 101206314 with filesize 1875 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:13:33: WARNING: File entry with id 101206317 with filesize 894 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:13:33: WARNING: File entry with id 101206319 with filesize 934 not found in entry index while deleting, but should be there. The file entry index may be damaged.
2016-06-03 12:13:33: WARNING: File entry with id 101206320 with filesize 1038 not found in entry index while deleting, but should be there. The file entry index may be damaged.

So i decide to run the repair-database but urbackupsrv repair-database failed twice :

root@urbackup:~# urbackupsrv repair-database
2016-06-03 12:31:20: SQLite: recovered 4102 frames from WAL file /var/urbackup/backup_server.db-wal code: 283
2016-06-03 12:31:20: SQLite: recovered 425903 frames from WAL file /var/urbackup/backup_server_files.db-wal code: 283
2016-06-03 12:31:20: SQLite: recovered 1 frames from WAL file /var/urbackup/backup_server_link_journal.db-wal code: 283
2016-06-03 12:32:00: Exporting database with id 20...
2016-06-03 12:34:34: SQLite: recovered 5 frames from WAL file /var/urbackup/backup_server_settings.db-wal code: 283
2016-06-03 12:34:34: Exporting database with id 30...
2016-06-03 12:34:34: Exporting database with id 23...
2016-06-03 12:45:29: Exporting database with id 24...
2016-06-03 12:45:29: Exporting database with id 25...
2016-06-03 12:45:29: Importing database with id 20...
2016-06-03 12:50:25: Importing database with id 30...
2016-06-03 12:50:25: WARNING: SQLite: table settings already exists errorcode: 1
2016-06-03 12:50:25: ERROR: Error preparing Query [
CREATE TABLE settings (key TEXT,value TEXT , clientid INTEGER)]: table settings already exists
2016-06-03 12:50:25: ERROR: Importing database failed
root@urbackup:~# urbackupsrv repair-database
2016-06-03 12:51:27: Exporting database with id 20...
2016-06-03 12:53:39: Exporting database with id 30...
2016-06-03 12:53:39: Exporting database with id 23...
2016-06-03 13:04:45: Exporting database with id 24...
2016-06-03 13:04:45: Exporting database with id 25...
2016-06-03 13:04:45: Importing database with id 20...
2016-06-03 13:09:40: Importing database with id 30...
2016-06-03 13:09:40: WARNING: SQLite: table settings already exists errorcode: 1
2016-06-03 13:09:40: ERROR: Error preparing Query [
CREATE TABLE settings (key TEXT,value TEXT , clientid INTEGER)]: table settings already exists
2016-06-03 13:09:40: ERROR: Importing database failed
root@urbackup:~#

What could be the matter ?

Regards,

zenekbg · June 3, 2016, 3:33pm

I have a problem whit Ubuntu 16.04 Urbackup Server 2.0.25
I cant make special btrfs RAW backup („punch holes“ into a file.)

znk@Ub-B1:~$ sudo urbackupsrv remove-unknown
2016-06-03 18:10:32: Going to remove all unknown files and directories in the urbackup storage directory. Waiting 20 seconds…
2016-06-03 18:10:52: Shutting down all database instances…
2016-06-03 18:10:52: Opening urbackup server database…
2016-06-03 18:10:52: Testing if backup destination can handle subvolumes and snapshots…
ERROR: not a btrfs filesystem: /mnt/sda/testA54hj5luZtlorr494
TEST FAILED: Creating test subvolume failed

from web interface Backup storage path: /mnt/raid10/ur1
from web interface i dont have Image backup file format: special btrfs incremental

/etc/fstab:
UUID=ba5d5b31-dbcd-4613-9b5a-331ac8b234ba / ext4 errors=remount-ro 0 1
UUID=4c49597c-a7a3-4e0e-ba22-230e58da458d /mnt/raid10 btrfs noatime, autodefrag

znk@Ub-B1:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 3.7T 0 disk /mnt/raid10
sdb 8:16 0 3.7T 0 disk
sdc 8:32 0 3.7T 0 disk
sdd 8:48 0 3.7T 0 disk
sde 8:64 0 3.7T 0 disk
sdf 8:80 0 111.8G 0 disk
└─sdf1 8:81 0 111.8G 0 part /

sdf is a ssd whit ubuntu 16.04
/mnt/raid10 is btrfs whit raid5

znk@Ub-B1:~$ btrfs ver
btrfs-progs v4.4

uroni · June 3, 2016, 3:37pm

Those warnings are normal after a server crash. I think I’ll remove them as they only confuse.

The repair is broken 2.0.25. Will be “repaired” with 2.0.26, but meanwhile you’ll have to restore the database from backup as the repair merged it wrongly.

(defrag rebuild the file index, but that is broken as well. Just deleting /var/urbackup/fileindex and restarting the server works currently)

TomTomGo · June 3, 2016, 4:15pm

Okay thanks !

I’ve stopped the server, delete files in /var/urbackup/fileindex and start the server again.
Now it’s rebuilding indexes :

2016-06-03 17:58:42: WARNING: Creating file entry index. This might take a while...

Do i really have to restore the database from the backup ? Because i’ve disabled “Automatically backup UrBackup database” in the GUI as it was too long and buggy with our large install …

Regards,

drenda81 · June 3, 2016, 7:30pm

Hi,
when do you think urbackup 2 will exit from beta phase?

There is a release plan?

Thanks

TomTomGo · June 6, 2016, 8:16am

Again this morning, lot of clients full image backup have Warning and Errors :

All with some wrong block messages like this :

Should it be a BTRFS issue (going to try a btrfsck …) ? Database issue ? Client issue ?

Regards,