Replica fails due to fault.duplicatename

I am currently waiting for a response from tech support on this. It seems that I would need to create a scheduled backup instead of replication. This would handle keeping X number of backups. However, what I had wanted was to keep an up to date replica which could be switched on quickly.

If this is not possible then I wonder what the purpose of changed block tracking would be? Is there still an advantage to this in the speed of creation of the replica if the entire vm replica has to be remade every time?

I think this was because I was, for testing purposes, replicating a VM back to the same server. Until our 3rd server is online I suppose I will have to replicate live VMs on one server to the other server and vice versa, even though they end up on the same datastore.

I hate to keep replying to myself here. But, fyi, I have an open ticket for this persistent problem.

I just tried a demo of a well-known competing product. I got the same duplicate name error when trying to create a replica of the same name. So, ultimately the error message is coming from vSphere (ESXi 4.1).

However, Acronis continues to have trouble with certain machines, whereas the other product handles the same VM source just fine, even on subsequent replications.

Hello Miles,

thank you for using Acronis Software.

Unfortuniately, there is no solution available for this issue. Please check first this steps:

• Always use the latest build of Acronis Products. For vmProtect 7 its currently 5155. How you can find the latest version for downloading, see here.
• Check if for the virtual Machine, that you attempt to backup, a snapshot can be created via ESX Host in your vCenter Client. If not, please contact VMware Support in order to get the snapshot up and running again.

If this does not help to solve your issue, please collect this Information:

• Used ESX Environment (4.x, 5.x, etc), Number of Hosts, Number of Sockets
• Number of virtual guests on the environment and number of affected machines
• Are you using Windows Agent (ESX(i)) or virtual Appliance?
• When using the Windows Agent, please collect Acronis Info.
• Screenshots from your Backup plan (complete, best in edit mode) and the vault.
• Save the logs out from the Web based GUI.
  - connect to the web interface
  - click on view and then on view logs. Click then into the log overview and then save all to file.
• Save logs from ESX Host. See here, how to do this.

Create a ZIP Archive from this informations and contact Acronis Support. Additional Information about this step, you will find here.

If there is anything else, we can do for you, please let me know. 

Thank you.

Thank you. But, I have already sent this information to support. I have not heard back from them in a week. We are using the virtual appliance and it is the latest version.

I have a competing product installed as a demo which is able to replicate the problem VMs. Since they are using snapshots and CBT I would guess that there is no issue with this on my servers. Both of my servers are having trouble but only with certain VMs. Surely, with the information I have sent them a week ago support can say whether or not there is a difference with those VMs that is at least a potential cause.

I have verified that the problem machines have VMWare Tools installed. These VMs are a mix of Centos 5.X, 6.X, and Windows Server 2003 and 2008R2.

If I delete the files and remove the replicas from inventory, then I can replicate them again once. It is only when trying to update the replica that I have trouble. Yes, the error is coming from ESXi but I believe this is because Acronis' interaction with ESXi. FWIW, I am using ESXi 4.1 update1. I want to update that to update2 and may have time over the long holiday weekend in two weeks.

Hello Miles,

thank you for this information. I have updated the Support Professional about your post here and asked him to contact you, in order to get a solution for you.

If there is anything else, we can do for you, please let me know. 

Thank you.

I haven't heard from them yet.

I've got the exact error as well. --> fault.DuplicateName.summary

The inital replica went over fine and I started it to test. The 2nd time the task ran I received the error fault.DuplicateName.summary

I don't know how many VMs you have. But, mine only failed on about half of them. Still waiting to hear something.

I have the same Problem and it is very very bad for us!!!

We found that this Problem is not on all VMs but in several Networks not at all VMs. There for it must be give a reason for this.

Hello Everyone,

thank you for using Acronis Software.

Unfortuniately, there is no solution available for this issue. Please check first this steps:

• Always use the latest build of Acronis Products. For vmProtect 7 its currently 5173. How you can find the latest version for downloading, see here.
• Check if for the virtual Machine, that you attempt to backup, a snapshot can be created via ESX Host in your vCenter Client. If not, please contact VMware Support in order to get the snapshot up and running again.

If this does not help to solve your issue, please collect this Information:

• Used ESX Environment (4.x, 5.x, etc), Number of Hosts, Number of Sockets
• Number of virtual guests on the environment and number of affected machines
• Are you using Windows Agent (ESX(i)) or virtual Appliance?
• When using the Windows Agent, please collect Acronis Info.
• Screenshots from your Backup plan (complete, best in edit mode) and the vault.
• Save the logs out from the Web based GUI.
  - connect to the web interface
  - click on view and then on view logs. Click then into the log overview and then save all to file.
• Save logs from ESX Host. See here, how to do this.

Create a ZIP Archive from this informations and contact Acronis Support. Additional Information about this step, you will findhere.

If there is anything else, we can do for you, please let me know. 

Please remember,

These steps are all checkt from me and other users but nothing happends. One of the reason to by this produkt is the function of generating Replicas from the VMs. Now we have pay the Price but the Software does not do the Job. That can´t be. We dont´t talk here about a small error that can happend. No, we talk about a General function from the Software witch MUST work !!!

Now in an other threat I must read that the actual version of Acronis VM Protect can´t backup Windows 2008 R2 ADS Server !!!!!!!!!!
That can´t be. Sorry but you are shure that this product is ready for the market. Sorry for these strong words, but this two function are basic funktions that must be ok. If not, this backup solution is not good for backup !

What can we Do to let the software do for what it is and we have paid???

Thanks

Hello Andreas,

Thank you for your reply.

I checked your account and saw valid support. I really recommend to step forward and contact our Acronis support. Acronis forums are not official support. You can find this information in our terms of use.

Understand that Acronis only Moderates the forum and does not have a commitment for answering all questions posted on the forum. If you are looking for certified Acronis Technical Support that you should submit a case by going to http://www.acronis.com/support/ and clicking on contact. Otherwise use the forum with the understanding that it is a community effort.

If there is anything else, we can do for you, please let me know.

Thank you.

Thank you Peter for the Info.

Hello Everyone,

The issue was caused by the fact that the original (replicated) VM had an .iso image attached to it. This .iso image was located on another datastore, different from the datastore which holds the original VM.

After the replication completes for the 1st time the replica VM appears to be located on 2 datastores at the same time and this is what is causing the problem.

The workaround is to detach (remove from the configuration) the .iso file from the original VM before doing the replication.

Please let us know if you need additional help.

Thank you.

This has resolved the problem for me.

My colleague followed the steps here as well. It's been working great already!