Dear All,
Did somebody experienced any problems with replication for vRanger 6.1 and ESXi 4.1 Update 3?
Our setup is :
- 2 IBM System x 3650 M3 servers with LSI2008 HBA connected to an IBM DS3500. Before upgrading to ESXi all the firmwares were upgrade including DS firmwares.
- Virtual center is installed on a virtual machine
- 1 IBM System x 3650 M3 used for disaster recovery ( on this server are hosted the replica VMs)
Last day I've upgraded vRanger 5.2.0 to the latest version and this because in 5.2.0 the replication did not worked ( https://support.quest.com/SolutionDetail.aspx?id=SOL83540&pr=vRanger)
After I deployed the appliance directly from vRanger console, I configured them with thin disks and started few small replication jobs. All the jobs completed ok, but over the night when the replication for our file server was active the host went down and we were forced to reboot it twice in order to restore the functionality.
When we searched for any orphan snapshot I noticed that on our virtual center there were a lot of them I I was forced to apply this http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004545
After I managed to consolidate the disks I wanted to delete the not used VMDKs, but this was not possible because I receive an error " Device or resource is busy"
After this I looked to see if there is any lock on those, but after following http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=10051 I did not noticed any lock so, I have tryied the following command:
find /vmfs/volumes/* -name *.vmx -exec grep -Hi VM name .vmdk {} \; which returned " Device or resource is busy" for all VMs from our environment, including the Powered Off VMs.
As a last resource I've stopped vRanger Appliances and gues what happened ? The error was gone and I managed to delete unused VMDK files.
Can some one telling me why this is happening?
Thank you,
Best Regards,
John