CBT Driver Error

client
1

Hello,
I am receiving this messages in one client using CBT Client. It was running with no problems before.
The client is Windows Server 2016 with urbackup client version 2.3.6.
The server is Debian 9 with UrbackupServer 2.3.8 with BTRFS filesystem.

The errors are:

Last driver log messages:
Failed to setup tracking for shadow copy \Device\HarddiskVolumeShadowCopy104 status c000000e
Failed to setup tracking for shadow copy \Device\HarddiskVolumeShadowCopy104 status c000000e
Failed to setup tracking for shadow copy \Device\HarddiskVolumeShadowCopy104 status c000000e
Failed to setup tracking for shadow copy \Device\HarddiskVolumeShadowCopy104 status c000000e

Any hints?

Thank you so much.

2

Sorry, you are having problems.

Could you have a look at the client log file ( described here Having problems with UrBackup? Please read before posting ) if CBT actually failed (CBT reset)?
Also if this CBT reset happend only once (e.g. because the shadow copy was deleted really fast after creation), it would not be that much of an issue… (if it happens regularily it is annoying). I guess the Windows event log entries w.r.t. HarddiskVolumeShadowCopy104 would also be interesting.

3

Hello,
This problem has been happening since a few days ago, I restarted server (Windows Server) and Debian (Urbackup Server) and the problem continues. I have also reinstalled UrBAckup Client. I don´t know if this uninstalls CBT driver also.

The client log is full of texts like this:

2020-05-20 11:30:28: WARNING: Parent of file with FRN 4503599628645181 (Name “TPT00010.DAT”) with FRN 6473924465619755 not found. Searching via MFT as fallback.
2020-05-20 11:37:29: WARNING: Parent of file with FRN 1970324838249333 (Name “TPT00010.DAT”) with FRN 2251799814959988 not found. Searching via MFT as fallback.
2020-05-20 11:37:29: WARNING: Parent directory not found in MFT. Was probably deleted.
2020-05-20 11:37:29: WARNING: Parent of file with FRN 7599824372462454 (Name “TPT00010.idx”) with FRN 2251799814959988 not found. Searching via MFT as fallback.
2020-05-20 11:37:29: WARNING: Parent directory not found in MFT. Was probably deleted.
2020-05-20 11:37:29: WARNING: Parent of file with FRN 1970324838249333 (Name “TPT00010.DAT”) with FRN 2251799814959988 not found. Searching via MFT as fallback.
2020-05-20 11:37:29: WARNING: Parent directory not found in MFT. Was probably deleted.
2020-05-20 11:37:29: WARNING: Parent of file with FRN 7599824372462454 (Name “TPT00010.idx”) with FRN 2251799814959988 not found. Searching via MFT as fallback.
2020-05-20 11:37:29: WARNING: Parent directory not found in MFT. Was probably deleted.
2020-05-20 11:37:29: WARNING: Parent of file with FRN 1970324838249333 (Name “TPT00010.DAT”) with FRN 2251799814959988 not found. Searching via MFT as fallback.
2020-05-20 11:37:29: WARNING: Parent directory not found in MFT. Was probably deleted.
2020-05-20 11:37:29: WARNING: Parent of file with FRN 7599824372462454 (Name “TPT00010.idx”) with FRN 2251799814959988 not found. Searching via MFT as fallback.
2020-05-20 11:37:29: WARNING: Parent directory not found in MFT. Was probably deleted.
2020-05-20 11:37:29: WARNING: Parent of file with FRN 7599824372462454 (Name “TPT00010.idx”) with FRN 2251799814959988 not found. Searching via MFT as fallback.
2020-05-20 11:37:29: WARNING: Parent directory not found in MFT. Was probably deleted.
2020-05-20 11:39:39: WARNING: Parent of file with FRN 2251799814960012 (Name “TPT00010.DAT”) with FRN 5348024558777224 not found. Searching via MFT as fallback.
2020-05-20 11:40:59: WARNING: Parent of file with FRN 1970324838249363 (Name “TPT00010.DAT”) with FRN 2251799814960018 not found. Searching via MFT as fallback.
2020-05-20 11:43:09: WARNING: Parent of file with FRN 3096224745092030 (Name “TPT00010.DAT”) with FRN 21673573207995323 not found. Searching via MFT as fallback.
2020-05-20 11:44:29: WARNING: Parent of file with FRN 4503599628645354 (Name “TPT00117.DAT”) with FRN 3377699721802729 not found. Searching via MFT as fallback.
2020-05-20 11:55:30: WARNING: Parent of file with FRN 3659174698513422 (Name “TPT00128.DAT”) with FRN 1688849861538828 not found. Searching via MFT as fallback.
2020-05-20 11:57:40: WARNING: Parent of file with FRN 1970324838249495 (Name “PRESTEL.DAT”) with FRN 3940649675224079 not found. Searching via MFT as fallback.
2020-05-20 12:03:20: WARNING: Parent of file with FRN 1125899908117575 (Name “TPT00086.DAT”) with FRN 2251799814960183 not found. Searching via MFT as fallback.
2020-05-20 12:15:36: WARNING: Parent of file with FRN 3940649675223466 (Name “buzentr.tmp”) with FRN 16607023625972834 not found. Searching via MFT as fallback.
2020-05-20 14:18:56: WARNING: Parent of file with FRN 1688849861538980 (Name “PRESTEL.DAT”) with FRN 3659174698513561 not found. Searching via MFT as fallback.
2020-05-20 14:55:19: WARNING: Parent of file with FRN 3096224745092285 (Name “PRESTEL.DAT”) with FRN 5348024558777530 not found. Searching via MFT as fallback.

4

If there is a error with the shadow copy tracking it’ll log

ERROR: Getting changed block data from shadow copy […]HarddiskVolumeShadowCopy104 failed: error message +code

Otherwise, this is just a problem with the initial setup and it succeeds when it retries.

The warnings you posted are unrelated.

In debug logging mode it’ll additionally log

DEBUG: Change block tracking reports X have changed on shadow copy

X is probably not accurate, but it shows that it is working.

5

It seems that some strange problem was in VSS storage. I have reinitialized the VSS storage for the volume and now it works. I will observe it the next days.
Thank you so much.