Replica is taking 2x disk space?

[vash]

I just tested replicating a VM and noticed the replica is taking 2x the disk space as the original. In the destination datastore, there is a file named "VMName_working.VMDK" that is the same size as the original VMDK. What's the function of this file? Is it safe to delete after performing a failover if the replica is to be used as production?

[Vitaliy S.]

Hello,

Replicated VM takes the same space as a source VM. You should not delete *_working.VMDK file. Please have a look at this topic for more information about this file: Replication question

Thanks!

[vash]

Cool. Thanks for pointing me to that post. I ssh'ed into the host and saw the true size of the *_working.vmdk file which is only about 400b.

[Vitaliy S.]

You're welcome. Good to know that you've figured it out.

[Nautilus]

[merged into existing discussion]

We migrate Veeam Backup & Replication from an older version to 5.0.1.198 x64.
We have vcenter 4.1 and ESXi 4.1 Hosts

We create all the replica Jobs new but after the relication Veeam is creating a normal file vm-name.vmdk and a second VMDK with vm-name_WORKING.vmdk with the same size.

What is this ......working.vmdk file and why veeam is creating this one. This is wasting double storage capacity.

How can i disable this option.

Thanks for any help