Backup Copy Job-bad length of vbk file

[martin.andres]

Hello,
I got some problem with Backup Copy Job.
In Veeam Backup&Replication 8.0 I created Backup job "Test1" as incremental. It created one VBM file, one VBK file 05.06.2016 (3 GB) and four VIB file from 06. to 09.06.2016 (all are 31MB (31 612 416 B)).
I wish keep some full backup files, for example 3 daily, 4 weekly, one monthly.
So 7.6.2016 I created Backup Copy Job: Backup Copy-VMware-set some name, -next- Virtual machines-Add-From Backups-select "Test1", Next- Restore points to keep=3, Keep following=4 weekly,1monthly, -next....Finish. In target directory are one VBM file, one VBK and some VIB files, all VBK and VIB are 31 584 256 B length. Why it create so small files (31MB) instead of full backup files (3GB)?
Now I try set Weekly backup at Friday 10:10. It create 10.6.2016 10:10 VBK file 31 584 256B length.
How can I set Backup Job to create correct VBK files with correct length?
Thank You.

[foggy]

Martin, can you please confirm that the jobs are successful and do not report any errors/warnings?

[martin.andres]

There ate no errors and warnings for this job.
Double click on Backup copy job"bcj2":
Job started at 10.06.2016 9:59:04 (is is when I edit settings to Friday week backup at 10:10)
New Copy Interval started
Building VM list 0:00:32
Waiting for new restore points 3:03:11

By VM name is written "Pending" and "No restore points found 3:03:11").

Backup copy job "bcj2" can't find backup data from backup job "Test1"? "Test1" job runs every day cca at 22:00.

[foggy]

Seems that there're no fresh restore points within the copy interval. How about the source backup job, did it complete fine on 6-9.06? Looking at the increment file sizes, it does not. I'd contact support for a closer look at what happens.

[martin.andres]

I resolve the problem. The problem was in target repository. There was only one repository so the source and target repository was the same.
It isn't possible to use the same repository as source and target for backup copy job. I found it here:
veeam-backup-replication-f2/backup-copy ... 22492.html
I created new repository (new shared folder on the same physical repository) and set it as target. Now it works fine.
Thank You.

[foggy]

Correct, glad you've nailed it. I believe v9 detects this and prompts a warning, so you shouldn't stuck into the same issue with it.