Provisioning failure, ufa error.

[Ricklm]

Info on setup... We have a main office and a few branch locations. Main office has Vcenter/view composer server. Branch offices each have a standard connection server install. One branch is working fine, how ever the new one i am in the process of setting up is having a few issues. Note one difference, the working office is connected to main office via vpn, the other is over metro-ethernet. I notice when I provision the new office after vm creation a large amount of data is passing from the view composer server to the esx server and the branch office, i dont recall seeing this with the other offices. This results in a very long provisioning time, or the following error and no provisioning at all.

FATAL | CommonLib.UfaSubsystem.UfaWorkItem - UFA error: fail in disk format operation.

INFO  | CommonLib.UfaSubsystem.InitializeDiskUfaWorkItem - UFA error: fail to finish init disk operation for disk: datastore:

FATAL | CommonLib.UfaSubsystem.UfaSubsystem - UFA error: operation failure thrown from work item execution.

FATAL | CommonLib.UfaSubsystem.UfaWorkItem - UFA error: format operation is aborted due to timeout: 1200000

Any idea what is being transfered? I suspect do to the slower connection this is the problem. However with the connection server local I'm not sure why so much data is going across.

Thanks for your time.

[Ricklm]

Also note that vmware-ufad.exe on the composer server is sending and receiving a lot of data to/from esi host during provisioning. Don't believe this is happening with the other location. Or at least not to the same extent.

[mittim12]

So each branch office has it's on View environment that each have a unique ADAM database?  

[Ricklm]

Yes, the main office hosts the vcenter and composer server. Then each branch has its own view connection server installed as standard, w/ adam. I was under the assumption you could not have multiple composer servers, i may be wrong.