Replication adding extra vhdxs with "0" and "01" appended

[rriiicchh]

Hello,

I am trying to replicate a VM with 14TB of data over a 50Mb link (which is fun).

The initial replication job failed due to non Veeam issue however running subsequent runs everything seems to be running from CBT which is good. Now the second run failed due to the checkpoint timing out after 72 hours but I've applied the appropriate registry key to prevent that going forwards.

My question is:

For my other VMs that are replicated the folder structure shows:

Cdrive.vhdx
cdrive.avhdx
cdrive2.avhdx

With an avhdx for each checkpoint

Whereas for this VM the structure is
Cdrive.vhdx
Cdrive_1.vhdx
Cdrive_01.vhdx

Which is a vhdx for each checkpoint.

Is this normal?

I am about to run the next job to hopefully complete everything however I don't want to wait 3ish days to find out that it is doing a full replica job and ultimately die due to space on the replication target because it had previously replicated 10TB so I was hoping it'd just grab the extra 4TB rather than replicating 14TB again. I'd rather cut my losses and delete it and start the whole process again if it is just going to fail in a few days time due to space.

[foggy]

Basically, the job should resume transfer from where it has stopped (check the working snapshot on the replica VM, if it is there, the job should continue writing to the next working snapshot). Haven't you thought about seeding the job, btw?