hussainbte's Accepted Solutions

The only change is that you have upgraded to vmfs6 and the snapshots are all sesparse. If you have a vmfs datastore which is still vmfs5 you can try and migrate the vm to there and take snapshots and check.. check if you have a local datastore which can be used for testing..

There is no way to send the ICMP request through a particular nic if the vSwitch has more than 1 vmnic you will have to play with active/passive nics. If you are looking to check the vLANs available on a particular nic you can use below command and check. its pretty helpful. vim-cmd hostsvc/net/query_networkhint | less

The maximum file size on a newly created vmfs5 is 2TB-512Bytes. The maximum file size on a vmfs3 datastore(or a vmfs5 datastore which was upgraded from vmfs3) formated with 1MB block size is 256 GB. And the file size for your VM is slightly greater than 256 GB and the destination vmfs3 datastore does not support this. Check the linked KB to get complete understanding. FYI a clone VM task requires a quiesed snapshot to be taken of the VM. Creating a snapshot for an ESXi/ESX virtual machine fails with the error: File is larger than maximum file size supporte…

It is not necessary to have your SRM and your vCenter powered on in your production site in case of an actual disaster. SRM server on the DR site can initiate a forced failover. It only needs to have access to DR storage. It is also not required for the Storage to communicate between sites, as you expect in a disaster situation the whole datacenter is does. so the recovery solutions are expected to be independent of anything in the primary location.

What is level of permissions given to the user in vCenter. Also make sure he is a SRM administrator for both Sites. This is from SRM admin guide "SRM determines if the operation is permitted when protection is configured, rather than at the time the operation is to be completed. After SRM verifies that the appropriate permissions are assigned on vSphere resources, future actions are carried out on behalf of users by SRM using the vSphere administrator context. For configuration operations, user permissions are validated when the operation is requested. Other operations require two phases of validation. 1 During configuration, SRM verifies that the user configuring the system has the required permissions to complete the configuration on the vCenter object. For example, a user must have permission to protect a virtual machine and use resources on a secondary vCenter Server that the recovered virtual machine would use. 2 The user executing the configuration must have permissions to complete the task. For example, a user must have permissions to execute a recovery plan. The task is then completed in the administrative context. "

Check for the esx.conf file in /etc/vmware. If you could also share a copy with me.. VMware KB: Attempting to mount the NFS volume fails with the error: Unable to resolve hostname Check the below link as well. http://www.bussink.ch/?p=1640

I have gone through the Database best practices link in the doc you shared. strange that VMware has not mentioned this clearly anywhere if it is good to keep the DB and vCenter app on separate machines. Need some concrete documentation that can back it up. Thank you for your update:)

The physical CPU utilization of the ESX host is done by scheduling the allocated vCPUs on all physical CPUs. General recommendation is to keep 1 core per socket and assign 12 vCPUs, until and unless there is specific requirement. Also if a 12 vCPU Virtual machine is CPU intensive it will use all the 12 physical CPUs on ESXi. kindly check if there are any other powered on VMs on the same host and move them to a different box.

I believe the switch has been deployed as a OVF in the vCenter. kindly download and save the extension.xml after accessing the switch IP from a browser and try to register it using the instructions given below. http://virtuallyhyper.com/2012/08/quick-step-by-step-guide-on-how-to-setup-the-nexus1000v-distributed-switch/