vThinkBeyondVM's Posts

whether there is any other operation being done on the same VM? can you check the VM file with .lck extension? if you can find such file, file name can give you idea on which VM it is referring t... See more...
whether there is any other operation being done on the same VM? can you check the VM file with .lck extension? if you can find such file, file name can give you idea on which VM it is referring to.
Both ideas would work fine with difference in downtime. As per me there is no concerns if you have same LUN attached to old ESXi and New ESXi. You can follow below option. 1.Attach same... See more...
Both ideas would work fine with difference in downtime. As per me there is no concerns if you have same LUN attached to old ESXi and New ESXi. You can follow below option. 1.Attach same LUN to new ESXi as well old ESXi(where old ESXi has placed VM folders), deploy new vCenter and add both new and old ESXi to new vCenter , then straightway vMotion & storage vMotion your VM files to New storage and New ESXi ...There will not be any downtime. You can even add old and new esxi to the same new vcenter cluster and use DRS/SDRS. There are no any major changes in DRS & SDRS features from 5.0 on-words. Note: You need to make sure vMotion/SVMOtion requirements are satisfied.
I agree with kashifkarar01. It is good to keep VM tools up to date.
Hi Mr VMware, VMFS 5 VMFS-5 uses a Unified Blocksize –> 1MB VMFS-5 uses smaller Sub-Blocks ~30.000 8KB blocks In VMFS-5, very small files (that is, files smaller than 1 KB) are store... See more...
Hi Mr VMware, VMFS 5 VMFS-5 uses a Unified Blocksize –> 1MB VMFS-5 uses smaller Sub-Blocks ~30.000 8KB blocks In VMFS-5, very small files (that is, files smaller than 1 KB) are stored in the location in the metadata rather than using file blocks. Once the file size increases beyond 1 KB, sub-blocks are used. After one 8 KB sub-block is used, 1 MB file blocks are used. As VMFS-5 uses sub-blocks of 8 KB rather than 64 KB (as in VMFS-3), this reduces the amount of disk space being used by small files. 130690 number is approximate. It would change based on individual file size. This discussion is worth to read: Re: Max number of files in a vmdk files, in VMFS5 format PLz refer for more details:VMware KB: Frequently Asked Questions on VMware vSphere 5.x for VMFS-5 ------------------------------------------------------------------------------------------------------------------------------------------------------------------ Plz award points if it is useful. Message was edited by: vVision
Refer :VMware KB: EVC and CPU Compatibility FAQ & Enhanced vMotion Compatibility - frankdenneman.nl These resources would increase your EVC understanding greatly.
It depends, This service  plays key role for storage profiles. Lets say, you want to provision one VM and attache done particular storage profile to that VM & at the same time, if you resta... See more...
It depends, This service  plays key role for storage profiles. Lets say, you want to provision one VM and attache done particular storage profile to that VM & at the same time, if you restart the service, this is going to affect the VM provisioning. Also if there are already some VM where you have system defined or user defined storage profile attached, you may not be in the position to check whether VM is storage profile compliant during the service restart time frame But once it is restarted it should continue to work as expected. Overall, only features those are dependent on this profile service would be affected for small duration. Message was edited by: vVision
Hi Friend, As per ESXi and vCenter server release notes : I do not see any references where windows 2012 is supported. Ref 1. VMware vCenter Server 4.1 Update 2 Release Notes 2. VMware vSphe... See more...
Hi Friend, As per ESXi and vCenter server release notes : I do not see any references where windows 2012 is supported. Ref 1. VMware vCenter Server 4.1 Update 2 Release Notes 2. VMware vSphere ESXi 4.1 Update 2 Release Notes On certificates front, there should not be any issue from vCenter functionality perspective. You will have default certificates installed.
Hi Friends, Do we get any advantage if we use IPMI over WOL or iLO while powering on host from standby mode?
I am not aware how it can be done by using vCO but we can schedule DPM feature enablement either by using web client/VI client scheduled tasks feature OR configure scheduled task by using VC-SDK.
Hi Friend, DPM puts standby host to ACPI S5 state which is just above the mechanical power off, it is mean that DPM tries to save as max power as possible. "The reason VMware DPM evacuates ... See more...
Hi Friend, DPM puts standby host to ACPI S5 state which is just above the mechanical power off, it is mean that DPM tries to save as max power as possible. "The reason VMware DPM evacuates hosts and powers them down to the ACPI S5 state is that hosts typically use 60 percent or more of their peak power when totally idle, so the power savings possible with this approach are substantial. Vacating a host and placing it in a lighter sleep state than S5, such as the ACPI S3 “suspend-to-RAM” state, can consume an order of magnitude more power than ACPI S5 because of the need to keep the host’s RAM powered on. Plz refer attached image for more details. If DPM puts host to ACPI S3 level, then host would take less time to get powered ON. But in the current design its not available to set DPM to ACPI S3 level. One more reason DPM takes more time to power on the host, If host has too many data stores attached to it. It does take more time to get powered ON. Also DPM uses 3 protocols : VMware DPM can use one of three power management protocols to bring a host out of standby mode: Intelligent Platform Management Interface (IPMI), Hewlett-Packard Integrated Lights-Out (iLO), or Wake-On-LAN (WOL). Each protocol requires its own hardware support and configuration. If a host does not support any of these protocols it cannot be put into standby mode by VMware DPM. If a host supports multiple protocols, they are used in the following order: IPMI, iLO, WOL. I suggest you to try enabling each one and compare, we may get some improvement over other. Please refer below KB: VMware KB: Configuring vSphere Distributed Power Management advanced settings to customize host power-on and power-o… This KB can satisfy your requirement by some other way for sure.  Just play with all advanced options available@KB If this info is useful, please award points as appropriate. Message was edited by: Vikas
switch to Round Robin Change path to storage to Round Robin from Most Recent used Please see above posts if these are of any help to you. I will come back tomorrow with more insight into it.
The reason could be high network/IO intensive operations are going on your VC VM . When we trigger vMotion, vMotion keeps the track of changed memory pages in order to be consistent at destinatio... See more...
The reason could be high network/IO intensive operations are going on your VC VM . When we trigger vMotion, vMotion keeps the track of changed memory pages in order to be consistent at destination host. If amount of memory getting changed is very frequently & greater than the available network bandwidth. vMotion will not get enough bandwidth to copy the changed memory pages at the destination host. Hence, vMotion fails. It is better if you migrate this VM in NON-peak hours. -------------------------------------------------------------------------------------------------------------------------------- Award points if you it is useful. ---------------------------------------------------------------
The reason could be high network/IO intensive operations are going on your VC VM . When we trigger vMotion, vMotion keeps the track of changed memory pages in order to be consistent at destinatio... See more...
The reason could be high network/IO intensive operations are going on your VC VM . When we trigger vMotion, vMotion keeps the track of changed memory pages in order to be consistent at destination host. If amount of memory getting changed is very frequently & greater than the available network bandwidth. vMotion will not get enough bandwidth to copy the changed memory pages at the destination host. Hence, vMotion fails. -------------------------------------------------------------------------------------------------------------------------------- Award points if you it is useful.
It is LUN queue depth throttling aka device throttling. 
Yes, Snapshot for OS disk only would be small. Also if you want to relocate all virtual disk to one largest datastore, you can create datastore cluster add all these 3 datastore to the datastore ... See more...
Yes, Snapshot for OS disk only would be small. Also if you want to relocate all virtual disk to one largest datastore, you can create datastore cluster add all these 3 datastore to the datastore cluster, enable SDRS in automated mode. create VM-VMDK affinity rule for the VM whose all disk you want to keep on 1 largest datastore. SDRS would do it for you on your behalf.
Also, If you want to remove datastore cluster, you can just right click and remove. It will not remove datastore attached to host like host cluster. You can add either all VMFS or all NFS data... See more...
Also, If you want to remove datastore cluster, you can just right click and remove. It will not remove datastore attached to host like host cluster. You can add either all VMFS or all NFS datastores into the datastore cluster but can not both in a datastore cluster
VMware vSphere® Storage APIs – Array Integration (VAAI), also referred to as hardware acceleration or hardware offload APIs, are a set of APIs to enable communication between VMware vSphere ESX... See more...
VMware vSphere® Storage APIs – Array Integration (VAAI), also referred to as hardware acceleration or hardware offload APIs, are a set of APIs to enable communication between VMware vSphere ESXi™ hosts and storage devices. Best resource to learn: vStorage APIs for Array Integration aka VAAI - Yellow Bricks http://www.vmware.com/files/pdf/techpaper/VMware-vSphere-Storage-API-Array-Integration.pdf
This is more close resource to get answer. http://www.vmware.com/files/pdf/vmw-vsphr-5-1-stor-drs-uslet-101-web.pdf
Hi Babu, See if this works for you 1, First you install latest powerCLI in a Windows VM where PowerShell is there (PowerCLI is snap-in on the top on windows Powershell). 2. Connect to VC... See more...
Hi Babu, See if this works for you 1, First you install latest powerCLI in a Windows VM where PowerShell is there (PowerCLI is snap-in on the top on windows Powershell). 2. Connect to VC . Use below command before running below script: #Below command will connect PowerCLI snapin internally. Add-PSSnapin Vmware* -ErrorAction SilentlyContinue #First command, Enter VC/VCVA IP (linux VC)   i)Set-PowerCLIConfiguration –ProxyPolicy ‘NoProxy’ -Confirm:$false   ii)$VCVAIP = Read-Host " `n `n Please enter the VCVA IP Address::" #Second command Set-ExecutionPolicy unrestricted #Third command Connect-VIServer -Server $VCVAIP -User "USERNAME" -Password "PASSWORD" Save below script in file say, "SVM.ps1" and then run the same as you run shell scripts. $Source_Datastore = get-vm "VM-Name" | Get-Datastore $i=1 while($i -eq 1){ if ($Source_Datastore.Name -eq "DS1"){ get-vm "VM-Name" | move-vm -Datastore DS2 Start-Sleep -s 20 $Source_Datastore = get-vm "VM-Name" | Get-Datastore } elseif ($Source_Datastore.Name -eq "DS2") { get-vm "VM-Name" | move-vm -Datastore DS1 Start-Sleep -s 20 $Source_Datastore = get-vm "VM-Name" | Get-Datastore get-vm } } Note: PLz give proper VM-Name and Datastore name as per your setup Regards Vikas, VCP 5.0, MSTS. If the answer is useful,please award the points as appropriate. Message was edited by: vickyvision2020
we looked at our backups to see how much new data was being stored every day across our VMs How did you check above details? Size of first iteration of replication would be more as enti... See more...
we looked at our backups to see how much new data was being stored every day across our VMs How did you check above details? Size of first iteration of replication would be more as entire disk would be replicated. After that VMware replication is expected to replicate only data that is being changed since last replication window. Increasing RPO to 24 hrs would be loss of lot of data. Rather plz check once again all required VMware replication requirements met properly, Also understand RPO/RTO trade off. REf-RTO vs. RPO: How Much Downtime Are You Willing To Tolerate? at Cloud, Datacenter, Data Protection Services | Venyu Blog