CBT error during Incremental File backup

Running the following:
Server: 2.5.19 Beta Server OS is Debian 11 (Bullseye)
Window 10 64-bit Client: 2.4.11 (not CBT)

I was having issues with CBT version 2.4.12 so I removed it and installed the 2.4.11 non-CBT version.
This is a side issue, but it looks like CBT is still installed as I get the same error.
"Error reading last bitmap data for CBT for other"

Is specific to my PC as my wife’s Windows 10 has no errors or warnings for any backups with CBT client 2.4.12.

Full and Incremental backups and Full File backups are fine.

Complete Client log is below. PC name is BBQ. Part of Server log also.

Anyone have any idea what could cause this error ?

TIA


Client Log file:

Starting scheduled incremental file backup…
Selected no components to backup
Change block tracking active on volume C:
Error reading last bitmap data for CBT for other
Scanning for changed hard links on volume of “C:”…
Indexing of “C” done. 199938 filesystem lookups 0 db lookups and 0 db updates
bbq: Loading file list…
bbq: Calculating file tree differences…
bbq: Calculating tree difference size…
bbq: Linking unchanged and loading new files…
Waiting for file transfers…
Waiting for file hashing and copying threads…
Writing new file list…
All metadata was present
Transferred 2.11636 GB - Average speed: 36.1852 MBit/s
Time taken for backing up client bbq: 48m 40s
Backup completed with issues

========================================================================

Server log: I get the VSS errors from time to time also.

2022-04-01 15:35:08: ERROR: Error reading last bitmap data for CBT for other
2022-04-01 17:09:51: 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.
2022-04-01 17:09:51: WARNING: Writer IIS Config 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.
2022-04-01 17:09:51: WARNING: Writer BITS 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.
2022-04-01 17:09:51: WARNING: Writer MSMQ Writer (MSMQ) 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.
2022-04-01 17:09:51: 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.
2022-04-01 17:09:51: ERROR: Error reading last bitmap data for CBT for other
2022-04-02 20:41:21: ERROR: Error reading last bitmap data for CBT for other

Sorry you are having issues. To solve the problem the client (debug) log would be useful.
If possible, could you post it or send it?

This post describes how to change the client to debug logging, where it is stored and where to send it to if posting is not possible: Having problems with UrBackup? Please read before posting

Thanks!

The debug.log file has hundreds if not thousands of messages like the one below.
Debug.log.1 and debug.log.2 were just the same.

I can email it if you want, but all the messages are like the one below except different FRN numbers and different names.

2022-04-04 09:25:48: WARNING: Parent of directory with FRN 53480245575025303 (Name “00BE00000000029722C51980”) with FRN 11540474045137076 not found. Searching via MFT as fallback.
2022-04-04 09:25:48: WARNING: Parent not found. Was probably deleted.

Now look near the e.g. “Error reading last bitmap data for CBT for other” message. It perhaps logs what it is trying to read.

That CBT message is not in debug.log.
I got that from right clicking om the urbackup icon on taskbar, selecting logs, then opening one.
The entire contents of yesterdays is above.

EDIT: I don’t know where that log is kept or if there would be more information in it.

Any other thoughts ?

See the link in my post above.

No indication as to what file is the problem.

2022-04-07 22:24:54: ClientService cmd: #ImaFoEKxLNtIgFWInR5FL#2LOGDATA 1649391893 0-1649388762-Starting scheduled incremental file backup…
0-1649391261-Selected no components to backup
0-1649391261-Change block tracking active on volume C:
2-1649391261-Error reading last bitmap data for CBT for other
0-1649391261-Scanning for changed hard links on volume of “C:”…
0-1649391261-Indexing of “C” done. 200579 filesystem lookups 0 db lookups and 0 db updates
0-1649391261-bbq: Loading file list…
0-1649391262-bbq: Calculating file tree differences…
0-1649391263-bbq: Calculating tree difference size…
0-1649391263-bbq: Linking unchanged and loading new files…
0-1649391864-Waiting for file transfers…
0-1649391868-Waiting for file hashing and copying threads…
0-1649391869-Writing new file list…
0-1649391871-All metadata was present
0-1649391890-Transferred 4.37115 GB - Average speed: 61.9018 MBit/s
0-1649391893-Time taken for backing up client bbq: 52m 10s
0-1649391893-Backup completed with issues