deleted an unused replica file on the datastore

[ragazzi]

Hi,

In the VMware Infrastructure Client i saw a replica file which was not used anymore for provisioning desktops. So, I wanted to delete it. Since I couldn't delete it within the Infrastructure Client I deleted it on the datastore, which obviously was a mistake. Now the replica still appear in the Infrastructure Client. How can I delete fhr replica properly?

I'm really not sure, bit it seems that from this time on I got a lot more provisioning errors, although the desktop pool is based on a new snapshot with a new replica and source file. Is this possible?

Today I the provisioning stopped two times. After rebooting the server, all seem to work properly but following error still occur:

(Request3845) Request failed: com.vmware.vdi.ob.tunnelservice.cx: Failed whilst returning body: java.net.SocketException: Connection reset by peer: socket write error

(several of those):

No record found for item cn=51ab7000-d948-4099-96e4-5452b3112e33,ou=servers,dc=vdi,dc=vmware,dc=int

(Request3286) Request failed: com.vmware.vdi.ob.tunnelservice.cx: Failed whilst returning body: java.net.SocketException: Connection reset by peer: socket write error

Thanks

[ragazzi]

No ideas?

[Linjo]

Its probably still protected from deletion. Try to unprotect it with the SVIconfig utility:

Here is a how to: http://blogs.egroup-us.com/?p=409

Best regards,

Linjo

If you find this information useful, please award points for "correct" or "helpful".

[ragazzi]

Thanks for the link but I think it will no help me, since there is no replica stored in the Datastore. I deleted it succesfully.

Although there is no file anymore the replica is still shown in the Infrastructure Client. It seems to me, that there is still a database entry..

[WJST]

Just restart the vmware management service on the ESX server. That should fix it. Restarting the vCenter also should do the trick. I wrote a short article about why this is on my blog:

- http://www.wjst.nl

[ragazzi]

I followed the post in your blog. Unfortunately it did not held.

It still shows the replica in the VMWare Infrastructure Clients greyed out with a comment at the end...

It looks like this:

"replica-adfa4c89-ebfc-4e49-9eab-3070643db40c (No access)"

[WJST]

Is the VM still protected?

Run vmwarehealthcheck.pl on it to find out the details (using the VMWare perl toolkit, or VIper)

Unprotect it using sviconfig. (details for sviconfig and unprotecting: http://www.wjst.nl/?p=1)

By the way, you did give your VDM broker a restart didn't you and the desktop pool where this replica has been bonded to isn't there eighter?

- http://www.wjst.nl

[ragazzi]

for unknown reasons sviconfig says that the entity cannot be found (probably because it is deleted on the datastore?).

I installed the VMWare perl toolkit and run the vmwarehealthcheck. According to the report everything seems to be ok. The replica which (still) appears in the VMware Infrastructure client is not mentioned in the report.

I also had a look at the VIM_LC database, especially table dbo.SVI_REPLICA but I did not find the replica name....