moved to ew b&r server incl. repository

[frankive]

We just moved to a new b&r server (v9).
We did a restore of the configuration database and moved the backup files.
Created new repository, imported backups and mapped the backup to the jobs.
The source sms is on the same cluster as it was before.

When we run a new job, it will actually create a incremental backup but the size is the same as a full backup.

When we do the same for the backup copy job to a cloud repository the same happens but it actually creates the the sms as new sms.
Even i we map the backup files, it insist to transfer all the data and actually create new Vms instead of just being a new restore point of the existing (yes, i have also rescanned the cloud repository and mapped the backup to the job. The same vm is in the job after the migration.

What may cause this?

Thanks.

[foggy]

When we run a new job, it will actually create a incremental backup but the size is the same as a full backup.

This looks similar to as if VM ID's have changed. Do you see duplicate VM entries under the Backups node? I'd ask support to take a look at the database, VM ID's specifically.

[frankive]

Yes, it is duplicate. The funny part though is that when the duplicate "VM" is made in the backup, it actually removes a restore point from the other VM.
F.ex i have the server DC01 with 28 restore points.
After running the backup a few days, i have 2 DC01 server, 1 with 4 restore points, the other with 24 restore points...

[foggy]

The fact that VM's are duplicate after importing configuration is not expected, so please run this through our support for verification. Thanks.

[frankive]

caseid 01765863