UrBackup Server 2.1.4 beta/Client 2.1.4 beta

Testing
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)

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

  • Seek correctly in hash file after checksum error; Restart from last block if checksum for current block wasn’t received yet
  • Always allow client to select transfer compression also if it is disabled globally
  • Show more detailed connection settings log messages
  • Do not connect while a ping/pong packet is in flight
  • Allow selection of vhd files from multiple directories in image assembly
  • Consistent backup volume normalization to fix image backup groups scheduling
  • Set default global soft file system quota to 95%
  • Increase to two minute timeout for referencing/removing shadow copy
  • Fixed a few coverity issues
  • Always use SQLite WAL journal mode except for VACUUM
  • Updated SQLite
  • Fix getting free space with backslash on Linux
  • Install favicon via Makefile
  • Backup speed localization
  • Print image backup volume into log
  • Fix “ignore disk errors” not being displayed correctly for clients and groups
  • Fix js issue if there are no groups

Changes with client 2.1.4 beta

  • Allow resume of image backups without snapshots (e.g. SYSVOL and ESP)
  • Only use lseek with SEEK_HOLE on Linux
  • Ignore VSS writer status on shadow copy delete if not backing up with writer involvement
  • Fixed a few coverity issues
  • Use SQLite WAL journal mode for database
  • Updated SQLite
  • Use proper param string escape function to escape e.g. ‘+’
  • Separate CBT finishing of file and image backups with bitmap persistence
  • Improve error message if shadow copy cannot be found/created

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:

cd /var/urbackup && wget -r -l1 --no-parent --reject "index.html*" -nH -nd -N "https://ssl.webpack.de/beta.urbackup.org/Client/2.1.4%20beta/update/"

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

3

Thanks for this new release !
After upgrading from 2.1.3 to 2.1.4, groups display seems to be broken, displaying “1 2 3 4” instead of groups memberships :

Pasted image1187×770 24.4 KB

Pasted image941×510 24.7 KB

4

Thank you for the new update.
Urback-Server in Freenas jail is now working again. Compiling 2.1.3 was not possible.

5

Thanks for reporting. Will be fixed.

6

So normally the clients will update to the current provided client version.
When I updated from 2.0.36 to 2.1.4 server, the clients are still showing as running 2.0.34 according to the status screen on the server dashboard. I do have autoupdate checked, is there something I’m missing?

7

With image backup mode and “snapshotting together” enable, if one of the 3 volume backup failed (e.g C: D: and E:, C: failed) UrBackup restart the backup for each volume instead of only the failed volume :

Pasted image693×265 13.8 KB

Backup of volume C: (failed) :

Pasted image873×385 25.9 KB

Backup of volume E: (success) :

Pasted image857×356 22.8 KB

Bakup of volume D: (success) :

Pasted image824×344 21.9 KB

Then it restart another backup for the 3 volumes C,D and E (instead of only the failed C:) :

Backup of volume D: (success) :

Pasted image831×344 21.8 KB

Backup of volume E: (success) :

Pasted image819×340 22.5 KB

Backup of volume C: (success) :

Pasted image825×338 22.9 KB

Regards,

8

I believe since this is a beta release the updated client packages need to be added manually on the server itself. The clients will then pull their update from there.

:slight_smile:

9

@Uroni
Image backups with Group settings :

Pasted image1038×517 25.5 KB

Advanced section settings :

We want to backup only volumes C:, F: and T:, as specidfied in the “Volumes to backup” field.
But the image backup occurs on all volumes, C:, F:, E:, T: and G: :
Pasted image863×421 24.8 KB

If we activate “Separate settings for this client”, it works fine (with exactly the same settings).
Verified with 2 clients connected to 2 different UrBackup servers

Server 2.1.4 / Client 2.1.4 with CBT

Regards,

10

Debugging mode on the client helps :

With a client under group policy with :

Pasted image1032×514 23.1 KB

Client debug log output :

If we checked the “Separate settings” :

Pasted image1064×517 22.6 KB

Client debug log output :

Regards,

11

Found that it takes the value of the “General settings” instead of the “group settings” :

Pasted image1068×516 26.4 KB

Regards,

12

Thanks for the analysis! Seems it sends the wrong settings to the client. Will be fixed.

13

You’re welcome ! Found another problem …

After growing a client disk from 60 to 80 gb, image backup fails with some checksum errors :

Pasted image838×776 45.9 KB

Rebooting the client doesn’t help

Pasted image866×449 24.2 KB

Maybe the problem is on BTRFS side and forever incremental , always based on last snapshot, and disk size is not upgraded :

Pasted image748×542 144 KB

Full image backup doesn’t help because of the BTRFS layout / forever incremental …

Regards,

14

Have somebody reproduce this problem ?

Regards,

15

Thanks! Could reproduce. Will be fixed.

16

Thanks !
Do you plan to release a new beta soon ?

Regards,

17

A tad overkill , but i made a script to download the beta client

18

Noticed another issue happened on one system only (others so far updated to 2.1.4 and backed up without issue.) Any reason to be concerned?

Problem system is 2012 R2, all patched and rebooted:

11/21/16 07:49 DEBUG Getting client settings…
11/21/16 07:49 DEBUG Sending backup incr interval…
11/21/16 07:54 INFO Starting unscheduled incremental file backup…
11/21/16 07:54 DEBUG BVE1: Doing backup with hashes…
11/21/16 07:54 DEBUG BVE1: Doing backup with intra file diffs…
11/21/16 07:54 DEBUG BVE1: Connecting for filelist…
11/21/16 07:54 DEBUG BVE1: Waiting for filelist
11/21/16 07:54 DEBUG BVE1: Connecting for filelist (async)…
11/21/16 08:14 WARNING Writer Certificate Authority has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
11/21/16 08:14 WARNING Writer WMI Writer has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
11/21/16 08:14 WARNING Writer COM+ REGDB Writer has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
11/21/16 08:14 WARNING Writer NTDS has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
11/21/16 08:14 WARNING Writer DFS Replication service writer has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
11/21/16 08:14 WARNING Writer is in error state during snapshot creation. Writer data may not be consistent. This means the files open by this application (e.g. databases) will be backed up in a crash consistent state instead of a properly shutdown state. Properly written applications can recover from system crashes or power failures.

19

The next automatic backup failed as well - but the second attempt appears to be finishing (it’s in verify state currently.)

Here are the logs from the failed backup overnight:

2016-11-22 02:14:08(info): Starting scheduled incremental file backup…
2016-11-22 02:14:44(warning): Writer System Writer has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2016-11-22 02:14:44(warning): Writer SqlServerWriter has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2016-11-22 02:14:44(warning): Writer DFS Replication service writer has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2016-11-22 02:14:44(warning): Writer Certificate Authority has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2016-11-22 02:14:44(warning): Writer Dhcp Jet Writer has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2016-11-22 02:14:44(warning): Writer WMI Writer has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2016-11-22 02:14:44(warning): Writer NTDS has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2016-11-22 02:14:44(warning): Writer System Writer has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2016-11-22 02:14:44(warning): Writer DFS Replication service writer has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2016-11-22 02:14:44(warning): Writer Certificate Authority has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2016-11-22 02:14:44(warning): Writer Dhcp Jet Writer has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2016-11-22 02:14:44(warning): Writer WMI Writer has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2016-11-22 02:14:44(warning): Writer NTDS has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2016-11-22 02:14:44(error): Writer System Writer has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT
2016-11-22 02:14:44(error): Writer DFS Replication service writer has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT
2016-11-22 02:14:44(error): Writer Certificate Authority has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT
2016-11-22 02:14:44(error): Writer Dhcp Jet Writer has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT
2016-11-22 02:14:44(error): Writer WMI Writer has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT
2016-11-22 02:14:44(error): Writer NTDS has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT
2016-11-22 02:14:44(error): Writer is in error state during snapshot creation.
2016-11-22 02:14:44(info): Removing unconfirmed VSS path “.symlink_SqlServerWriter_{A65FAA63-5EA8-4EBC-9DBD-A0C4DB26912A}e38575f82272893d667ba26ee03bb3f5_master_files00000000" to "C:\Users\AAD_a0a92695ef65\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\ADSync
2016-11-22 02:14:44(info): Removing unconfirmed VSS path ".symlink_SqlServerWriter{A65FAA63-5EA8-4EBC-9DBD-A0C4DB26912A}_e38575f82272893d667ba26ee03bb3f5_ADSync_files00000000” to "C:\Program Files\Microsoft Azure AD Sync\Data
2016-11-22 02:14:44(warning): Writer System Writer has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2016-11-22 02:14:44(warning): Writer WMI Writer has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2016-11-22 02:14:44(warning): Writer Certificate Authority has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2016-11-22 02:14:44(warning): Writer DFS Replication service writer has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2016-11-22 02:14:44(warning): Writer Dhcp Jet Writer has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2016-11-22 02:14:44(warning): Writer NTDS has failure state VSS_WS_FAILED_AT_FREEZE with error VSS_E_WRITERERROR_TIMEOUT. UrBackup will continue with the backup but the associated data may not be consistent.
2016-11-22 02:14:44(error): Constructing of filelist of “BVE1” failed: error - index error
2016-11-22 02:14:48(error): Backup had an early error. Deleting partial backup.

20

Well strangely enough, today the backup ran without errors overnight. Guess whatever was wrong worked itself out.
I’ll keep an eye on it and post again if it comes back.