CBT Output Buffer Too Small

@Xkx420 wrote:

Hi Uroni, thanks for getting back to me I appreciate it.
I have changed the arg file to debug, had to stop the service and restart to get a clean log.
I have attached 2 logs, one is the old log which goes all the way back to the beginning and has a lot of misc stuff from where I was playing and messing stuff up lol. Shows a lot of errors but I have to admit to not knowing what any of it means. I have also made a clean log file from which the debug switch is turned on.

I have run 4 runs of urbackup, run one is an incremental image backup on the drive with almost no changes (previously run urbackup and Veeam only runs from dawn to dusk on this drive).
then I ran an incremental file backup.
After this almost no change to source run I have run an incremental image run and then an incremental file run.

I hope that makes sense and gives a benchmark or 2 to ref.
if you need more information please let me know.

Please forgive any errors as I am still learning how to use URbackup to a good degree.
That said it is a unique piece of software and it is doing for us what a lot of very expensive software cannot–safe offline internet transferred backup, awsome.
thanks
John

CBT Status window text
Volumes with active change block tracking with crash persistence (v2.13):
N:

Volumes without change block tracking:
E:, V:, I:, C:, T:, D:, F:

Last driver log messages:urbackup - Copy.zip (96.9 KB)
Output buffer too small (0) in IOCTL_URBCT_STATUS

Read full topic