Cannot complete the operation file or folder already exist

[phild]

Hi,

Using VEEAM 8 to backup multiple servers to an onsite datastore, then replicating the backups off site to a separate datastore.

All was all working well until the disk capacity on the DR site got low, then all the replications stopped, but after purging some old unwanted VM's the replications started again, and all picked up fine except the Exchange server.
The replication starts and then displays the error "Preparing replica VM Error: Cannot complete the operation because the file or folder already exists"

I followed the instructions on a couple of other threads and removed the old failed snapshots from the vm_replica, and now the disks all show as 0 size in the VM_replica settings with a red ! next to each disk, but in the datastore they are about the size i would expect to see.

The same error still exists, and trying to start the vm_replica fails.

I really dont want to have to remove the replica and stream another 550GB across the WAN, so hopefully there is a way to fix this.

regards

Phil

[PTide]

Hi,

Do you have your exchange replication proccess held in the same job as other VMs?

[Shestakov]

Hi, have you tried to remap the replica?
This topic may be helpful.
I would also suggest to contact Veeam technical support when face technical errors. Thanks!

[phild]

Hi,

Do you have your exchange replication proccess held in the same job as other VMs?

The replication job has its own process, but the actual backup for the Exchange server has another VM in the job, both 2008 servers.

Hi, have you tried to remap the replica?
This topic may be helpful.
I would also suggest to contact Veeam technical support when face technical errors. Thanks!

Yes i have tried to remap the replica, still the same issue.
The difference with the above topic is that the above gives a specific vmdk error, my issue has nothing apart from the error given.

i will raise a support ticket if i cant get any community help.

thanks

phil

[PTide]

Do you have a backup of your Exchange machine on your DR site? If so, then there is no need to transfer everything - you can use replica seeding. Please follow the link for details.

Also please post your support ticket number here, once you get one.

Thank you.

[phild]

PTide,

i did a test on small machine and used the replica seeding as in the link, where a restore is pushed to the destination then used as a seed.

Im not sure if i did it correct, as I was prompted that the existing files would be over written, which did seem to be the case.
That wasnt a problem with a 20gb image, but will be with 550gb.

Any other method of seeding i have tried also fails.

cheers

[PTide]

I apologize for giving you the wrong link (v.7), please make sure you do everything as it is described here.
If this article does not help then it's an unexpected behaviour and the only way to resolve the issue would be to open a ticket.

Thank you.

[phild]

i did notice that the previous link pointed to V7 and a further link to V8, so i followed that as well, but it still failed with the same error.

Looks like i will be raising ticket for this.

Thanks for the help.

Phil

[larry]

On the VC that holds the replica with the error
1) Do snapshot, consolidate
2) delete leftover delta files - only the delta files, you can use the vc gui to browse to the data store, delete the XXX-0000001.vmdk files

now snap shot should work again, test outside of veeam first.

[phild]

Thanks for the input on this. i opened a ticket with support, and they asked me to follow this which has fixed the issue, so all good now.
http://www.veeam.com/kb1773

Larry,
it would not allow me to consolidate, as i tried that a few days ago.

cheers
phil