Job Running Too Much time

[handian.sudianto]

Hello,

I have baremetal server backuped by veeam agent.
The job already configured and running from a month ago, but for incremental backup 2 days ago i found the backup taken too much time.
Usually the incremental backup running for 2 hours but 2 day ago the backup take more than 20 hours.
I have 2 disk backuped by veeam, one disk running for 11 minutes and the second disk take almost 17 hours, we can see in below link
https://ibb.co/G9Hx1KC
I want to know why on the 1st disk there are [CBT] and no for disk 2, also why disk 2 read almost reach the disk 2 capacity are this mean the agent do full backup for disk 2?

[haslund]

Just to clarify, the G: drive is not a new drive? So in the past only incremental backups? Did the drive size change or some other change occur?

[Mildur]

Hi Handian

Have you asked our support team already? That should always be your first point of contact in case you face a "technical issue". And not our forum.

For the missing CBT, I can only assume your drive G was formatted with ReFS? The Default CBT mechanism does not work for ReFS volumes. Our CBT driver would be needed.
Or this is the first time the job processes drive G. Active Full Backups will not leverage CBT. An Active Full Backup always needs to read every block from the source.

Best,
Fabian

[handian.sudianto]

Hi..

Job for previous and after that day showing the G drive use CBT, so the problem just only for that day only. Any potential root cause why on that day the G drive not use CBT?

[haslund]

Log access would be needed for that. Please open a support case. You can share the case number here.