Issues speed backup one client

ATP · February 17, 2022, 9:46am

Hello

Currently the server performs 4 backup tasks, 3 always work correctly, the problem is with one server. The problem is that it usually takes many hours to complete a backup.

There are days that it takes 3 or 4h, another day 6h, 18h, 19h, etc… the copied data is always about 10 GB only.

I bought a Change block tracking license to speed up the process, but nothing has changed.

URBACKUP SERVER
Windows server 2019
Urbackup 2.4.14

BACKUP
Windows server 2012 r2
Urbackup client 2.4.12-CBT

Today the copy started at 00:23 and it has not passed 0% and it is 9:29

15/02/22 00:04
Starting scheduled incremental file backup…
Informativos

15/02/22 00:08
Component caption= name=DEEPBLACK\SWPDM
Informativos

15/02/22 00:08
Component caption= name=DEEPBLACK\SWPDM
Avisos

15/02/22 00:08
Writer ASR Writer has failure state VSS_WS_STABLE with error VSS_E_WRITERERROR_NONRETRYABLE. UrBackup will continue with the backup but the associated data may not be consistent.
Avisos

15/02/22 00:08
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.
Informativos

15/02/22 00:08
Change block tracking active on volume c:
Informativos

15/02/22 00:08
Scanning for changed hard links on volume of “c:”…
Avisos

15/02/22 00:08
Writer ASR Writer has failure state VSS_WS_STABLE with error VSS_E_WRITERERROR_NONRETRYABLE. UrBackup will continue with the backup but the associated data may not be consistent.
Avisos

15/02/22 00:08
Writer ASR Writer has failure state VSS_WS_WAITING_FOR_BACKUP_COMPLETE with error VSS_E_WRITERERROR_NONRETRYABLE. UrBackup will continue with the backup but the associated data may not be consistent.
Avisos

15/02/22 00:08
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.
Informativos

15/02/22 00:08
Change block tracking active on volume E:
Informativos

15/02/22 00:08
Scanning for changed hard links on volume of “E:”…
Informativos

15/02/22 00:08
Indexing of “PDM” done. 732 filesystem lookups 313200 db lookups and 472 db updates
Informativos

15/02/22 00:08
deepBlack: Loading file list…
Informativos

15/02/22 00:08
deepBlack: Calculating file tree differences…
Informativos

15/02/22 00:08
deepBlack: Calculating tree difference size…
Informativos

15/02/22 00:08
deepBlack: Linking unchanged and loading new files…
Informativos

15/02/22 04:26
Waiting for file transfers…
Informativos

15/02/22 04:27
Waiting for file hashing and copying threads…
Informativos

15/02/22 04:28
Writing new file list…
Informativos

15/02/22 04:28
All metadata was present
Informativos

15/02/22 04:28
Transferred 10.4651 GB - Average speed: 5.79475 MBit/s
Informativos

15/02/22 04:28
Time taken for backing up client deepBlack: 4h 23m 58s
Informativos

15/02/22 04:28
Backup succeeded

uroni · February 17, 2022, 11:11pm

Maybe click on the show log button to see exactly what it does.
Then you’d need to check if the transfer is set to block hash in the advanced settings, otherwise CBT won’t work for the files.

ATP · February 20, 2022, 6:18pm

Hi,

Change the option “Local incremental file backup transfer mode:” from “Hashed” to “Block difference - hashed” but I haven’t changed anything.

Attached file with the result of the “show log” button
log.txt (54.8 KB)

BrainWaveCC · February 21, 2022, 4:52pm

Are you sure there’s no I/O error with the client system?

Are there any generic Windows error messages in the EventViewer?

ATP · February 23, 2022, 3:18pm

Hi BrainWaceCC

On this same server there are 2 different backups:

1.- Every day make a backup to a USB hard drive.
2.- Every week make a backup to an RDX unit.

In both cases without problems, in approximately 2 hours it performs the backup (differential).

Event Viewer, only found this:

Error: 0:09:06
Volume Shadow Copy Service error: Unexpected error calling routine IVssAsrWriterBackup::GetVolumeComponents. hr = 0x80073bc3, The requested system device cannot be found.
.

Operation:
OnIdentify event
Gathering Writer Data

Context:
Execution Context: ASR Writer
Writer Class Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Name: ASR Writer
Writer Instance ID: {200845f6-4840-45b2-95db-1b1a2cca6091}

Error: 0:09:07
Volume Shadow Copy Service error: Unexpected error calling routine Check OnIdentifyError. hr = 0x80073bc3, The requested system device cannot be found.
.

Operation:
PrepareForBackup event

Context:
Execution Context: ASR Writer
Execution Context: Writer
Writer Class Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Name: ASR Writer
Writer Instance ID: {200845f6-4840-45b2-95db-1b1a2cca6091}

Error-specific details:
ASR Writer: The requested system device cannot be found. (0x80073BC3)

Warning: 0:09:07
Volume Shadow Copy Service warning: ASR writer Error 0x80073bc3. hr = 0x00000000, The operation completed successfully.
.

Operation:
PrepareForBackup event

Context:
Execution Context: ASR Writer
Execution Context: Writer
Writer Class Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Name: ASR Writer
Writer Instance ID: {200845f6-4840-45b2-95db-1b1a2cca6091}

Error-specific details:
ASR Writer: The requested system device cannot be found. (0x80073BC3)

Error: 0:13:16
Volume Shadow Copy Service error: Unexpected error calling routine IVssAsrWriterBackup::GetVolumeComponents. hr = 0x80073bc3, The requested system device cannot be found.
.

Operation:
OnIdentify event
Gathering Writer Data

Context:
Execution Context: ASR Writer
Writer Class Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Name: ASR Writer
Writer Instance ID: {200845f6-4840-45b2-95db-1b1a2cca6091}

BrainWaveCC · February 24, 2022, 8:53pm

Have you tried a different USB drive just to verify that it is not something about the drive or the port that the system is connected to?

-ASB

ATP · February 24, 2022, 9:19pm

The USB disk, after performing the Backup, is automatically disconnected. It is only connected during the backup process so it does not interfere with Urbackup at any time.

ATP · March 1, 2022, 9:54am

This morning:

The backup starts at 00:00, at 9:27 the percentage bar in “progress” started to move. Currently (10:50) it stays at 98%…There are days when it takes about 3h/4h to finish the backup, on other occasions this happens…

UPDATE:
Backup completed, this is the log:

Info	01/03/22 00:04	Starting scheduled incremental file backup…
Info	01/03/22 00:07	Component caption= name=DEEPBLACK\SWPDM
Info	01/03/22 00:07	Component caption= name=DEEPBLACK\SWPDM
Info	01/03/22 00:07	Component caption= name=DEEPBLACK\SWPDM
Info	01/03/22 00:07	Component caption= name=DEEPBLACK\SWPDM
Info	01/03/22 00:07	Component caption= name=DEEPBLACK\SWPDM
Warnings	01/03/22 00:07	Writer ASR Writer has failure state VSS_WS_STABLE with error VSS_E_WRITERERROR_NONRETRYABLE. UrBackup will continue with the backup but the associated data may not be consistent.
Warnings	01/03/22 00:07	Writer ASR Writer has failure state VSS_WS_STABLE with error VSS_E_WRITERERROR_NONRETRYABLE. UrBackup will continue with the backup but the associated data may not be consistent.
Warnings	01/03/22 00:07	Writer ASR Writer has failure state VSS_WS_STABLE with error VSS_E_WRITERERROR_NONRETRYABLE. UrBackup will continue with the backup but the associated data may not be consistent.
Warnings	01/03/22 00:07	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.
Info	01/03/22 00:07	Change block tracking active on volume c:
Info	01/03/22 00:07	Scanning for changed hard links on volume of “c:”…
Warnings	01/03/22 00:07	Writer ASR Writer has failure state VSS_WS_STABLE with error VSS_E_WRITERERROR_NONRETRYABLE. UrBackup will continue with the backup but the associated data may not be consistent.
Warnings	01/03/22 00:07	Writer ASR Writer has failure state VSS_WS_STABLE with error VSS_E_WRITERERROR_NONRETRYABLE. UrBackup will continue with the backup but the associated data may not be consistent.
Warnings	01/03/22 00:07	Writer ASR Writer has failure state VSS_WS_WAITING_FOR_BACKUP_COMPLETE with error VSS_E_WRITERERROR_NONRETRYABLE. UrBackup will continue with the backup but the associated data may not be consistent.
Warnings	01/03/22 00:07	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.
Info	01/03/22 00:07	Change block tracking active on volume E:
Info	01/03/22 00:07	Scanning for changed hard links on volume of “E:”…
Info	01/03/22 00:07	Indexing of “PDM” done. 617 filesystem lookups 315221 db lookups and 541 db updates
Info	01/03/22 00:07	deepBlack: Loading file list…
Info	01/03/22 00:08	deepBlack: Calculating file tree differences…
Info	01/03/22 00:08	deepBlack: Calculating tree difference size…
Info	01/03/22 00:08	deepBlack: Linking unchanged and loading new files…
Info	01/03/22 13:44	Waiting for file transfers…
Info	01/03/22 13:44	Waiting for file hashing and copying threads…
Info	01/03/22 13:45	Writing new file list…
Info	01/03/22 13:45	All metadata was present
Info	01/03/22 13:45	Transferred 444.334 MB - Average speed: 76.096 KBit/s
Info	01/03/22 13:45	Time taken for backing up client deepBlack: 13h 41m 29s
Info	01/03/22 13:45	Backup succeeded

BrainWaveCC · March 4, 2022, 3:39pm

Are there any errors in the EventViewer logs for the UrBackup server and the UrBackup client?