Replication job ends with duplicated disk

[gacosta]

Hi every one.
I've created a new replication job of a vm with 2 disk (first with 30gb and second with 200gb) on a new datastore and it ends without problem.
When I check the new datastore I see 1 vmdk of 30 gb, and 2 disk of 200gb. One of them is a thin disk and the other is a thick disk.
The 200gb original disk is thik.
Even on the replica vm properties I see that it has a total of 3 disk.
Anyone can tellme why is this happening?
I'm using veem for a long time and this is the first time.

Thanks in advance.

[Vitaliy S.]

Hi Gabriel,

Have you recently performed any actions on the 200 GB disk of the source VM? Or changed job properties and especially virtual disk replication settings? If you boot this VM, do both disks have the same data (time stamps etc.)?

Thanks!

[gacosta]

If I boot only with the 30gb disk (O.S.) and the thin disk. The O.S. can't found that disk, but if I boot with the other disk (thick) theres no problem.
I didn't modified anything on the source vm.
The job was created with no changes on the options.
I've made a new replication of the same VM to other host and the problem persist.

[Vitaliy S.]

What kind of disk (200 GB) is this? Can you please review the corresponding job session (can be found in the history node of the backup console)? How many disks are processed from the source VM?

[gacosta]

We are using veeam v5.0 (I know it's old, but we can't upgrade until middle of 2014... long story) and it doesn't show me how many disks are processed.
I have an ubuntu partition on that disk with ntfs4. It's thick disk with a provisioned size of 200gb.

[Gostev]

I am afraid you cannot even get support on 5.0 any longer, so you are stuck until you upgrade...