uroni
January 17, 2017, 3:34pm
1
Major changes with server 2.1.x beta
Groups for client settings
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.14 beta
Use correct name for quick_check result (fixes false database corruption warning)
Fix issue with file patching sparse extent alignment
Updated SQLite to 3.16.2
Update LMDB to 0.9.19
Fix dead lock on Linux with pthreads
Fix bug with sparse extent resetting during chunked file transfer reconnect
Use scoped cursors during recovery
Require user to specify which image volumes to archive when configuring image backup archiving
Also use sparse block size to align sparse extents when patching
Fix verification of backupcom.xml and backup script files
Do not start backup if it cannot be added to the database (e.g. because out of space)
Use long polling to reduce request time to max 10s during image mounting
Changes with client 2.1.11 beta
Fix Windows component backup
Keep async index status around after async index is finished to prevent error after indexing is finished
Fix async mempipe timeout when there are not backup directories
Updated SQLite to 3.16.2
Fix transfer of metered info during CAPA transfer
Break from loop if sparse lseek does not move forward
Check for send errors at image backup end
Fix null pointer access after image backup read error
More efficient saved journal data application using database cursor
Fix journal replay after index
Windows backup API restore: Implement flag to ignore overwrite failures
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.
On Linux e.g. with this update script: https://github.com/ptempier/get_urbackupclient/blob/master/updateclient.sh
Downgrade process (server)
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.
Downloads
Oups, seems you forgot client sig files
uroni
January 17, 2017, 3:49pm
4
Thanks for the hint. Added them now.
mjyu51
January 19, 2017, 2:48am
5
Test report:
This is only a minor issue, but just wanted to clarify.
mjyu51
January 19, 2017, 3:03am
6
Another issue:
a text file with the original file name was “restored”, try to open it and it shows “Access Denied”
the renamed text file stays in the folder
uroni
January 20, 2017, 1:33pm
7
Could reproduce the first problem. Could you try to create a client debug log for the second case (access denied) and send me that?
mjyu51
January 20, 2017, 7:51pm
8
I will do this. I need a little bit time to re-install and create the same environment to reproduce the issue and send you the debug log.
mjyu51
January 21, 2017, 12:29am
9
Here is the debug file (on Windows 7 64bit machine):
uroni
January 21, 2017, 12:06pm
10
Could you put it into debug log mode please, such that it not only logs errors/warnings. Details on how to configure a client to do that are here: Having problems with UrBackup? Please read before posting
mjyu51
January 21, 2017, 6:53pm
11
uroni,
mjyu51
January 22, 2017, 6:00pm
12
uroni,
uroni
January 22, 2017, 9:10pm
13
Unfortunately there is some missing logging, I think. My working theory is that there is some missing/misplaced meta-data halfway through. I’ll add some logging, so maybe we get more information with the next version. Thanks!
mjyu51
January 22, 2017, 11:33pm
14
OK. Please let me know when it is ready and I will test it again
can’t compile Linux server version:
can you fix this error
Hot resizing a vm’s disk from 100 to 120 Gb (not the system one …),
UrBackup CBT Status shows :
Getting status of T: failed. Error code: 317
Change block tracking disabled
Volumes with active change block tracking and no crash consistency (v2.5):
E:, F:, G:, C:
Volumes without change block tracking:
D:
Last driver log messages:
Write outside of bitmap offset 128845872640 size 512 bitmap size 28672
Change tracking disabledChange tracking disabled in IOCTL_URBCT_STATUSThink i need to reboot the client to raise this error ?
Regards,
FYI, got this message after reboot :
Regards,
Resizing client hard drive result in server’s crash while trimming :
Server log :
2017-01-24 11:01:48: WARNING: Reading from parent hash file failed (may be caused by a volume with increased size)
2017-01-24 11:01:48: Trim beyond drivesize (drivesize: 128846396928 trim to 128846397440). Trimming less...
2017-01-24 11:01:49: Starting trimming image file (if possible)
2017-01-24 11:05:34: Trimmed 1.24512 GB
uroni
January 24, 2017, 11:39am
19
Look like it happens somewhere after trimming. Do you have full logs or backtraces?
uroni
January 24, 2017, 11:48am
20
I think you are using the debian package. In this case setting it up to collect core dumps and sending me them would help as well.
Edit: I think this might be the easiest method: http://stackoverflow.com/a/18400/506718
