Full Backup instead of incremental after seeding a backup

[US2015]

Hi All,
I have ran into this issue multiple times, but haven't any found a solution yet. Any help would be highly appreciated.
Problem is,
When I run a seeded backup job, it always starts from full backup instead of incremental.
Have checked all the setting and made sure newly copied job is exact replica of old job.

wondering if anyone else has ran into these things as well.

Thanks
US

[veremin]

When I run a seeded backup job

Can you describe the exact steps of how you seeded and mapped a backup job?

It always starts from full backup instead of incremental

How did you understand that? Did it take more time to finish? Or the size of increment was comparable to the size of full backup?

Thanks.

[Jackf]

Hi,

I have the same issue. I Seeded the data to a local NAS. I then transferred the NAS to a different geographical site and created a new job from another Veeam server pointing the repository at the seeded data.

The backups on disk show correctly ie FULL, INCREMENT, INCREMENT etc for the VM in question.

Then for no apparent reason at all is decides to do a FULL.

This is a real issue as the VM is 1.7tb's in size and i cannot have this performing a FULL over the WAN.

[foggy]

Jack, could you please answer the questions Vladimir has asked above? Did you follow this seeding procedure?

[Jackf]

Yes.

1. I ran a NEW Full backup to a local NAS repository.
2. I physically transported this NAS to our datacentre.
3. On a operate Veeam server in the DC i created a repository and pointed it to the exact path of the seed data.
4. Created a new job on the veeam server in the DC, added all the VMS's in and picked the backup repository, selected map backups then mapped to the existing backup.
5. Ran the Job. This ran on every VM using the seed. expect 1. (the file server)

I know this because when you select Backups on Disk. Right click the backup containing all the VM's > select the VM's in the right hand pane it shows FULL > INCREMENT > INCREMENT

However for the file server it shows FULL > INCREMENT > FULL

Why is it that veeam decides to just do a full when an OK increment is present?

I have seen this twice now. not only with Seed data.

Scenario 2

1. Created a new Job
2. Ran the New Job.
3. Can see all VM's have now completed successfully.
4. Re-run the job.
5. can see all VM's have an OK increment.
6. Start the Job again.
7. Can see that 1 VM is taking longer than the rest
8. Check the backups on disk and this has decided to do a FULL for no apparent reason.

This scenario involved no change in job or seed data.

[veremin]

The way you've described it makes the situation look unexpected, indeed. So, it's certainly worth reaching support team for closer investigation. Thanks.