ramakrishnak's Posts

by default the VM storage policy is 1 Failure to Tolerate. that means 2 copies of VM data. hence the behavior you are seeing. if you don't care about the availability of the data then you can ... See more...
by default the VM storage policy is 1 Failure to Tolerate. that means 2 copies of VM data. hence the behavior you are seeing. if you don't care about the availability of the data then you can configure the Storage policy and set it to 0 Thanks,
Certification plan for PCIE SSDs for VSAN 6.0 is in progress. hence this is not yet showing up in HCL Thanks,
can you check whether you have valid license on all these hosts ? and also are all in par with the ESX build versions among them Thanks,
AFAIK Migration is not supported on VMs with SCSI Bus Sharing mode (virtual|physical) Thanks,
yes, correct. sorry you misunderstood what i mentioned what am saying is in this case, there is two failures, resulting in both copies unusable, we don't handle double faults and the VM c... See more...
yes, correct. sorry you misunderstood what i mentioned what am saying is in this case, there is two failures, resulting in both copies unusable, we don't handle double faults and the VM cannot be recovered in such cases now i agree with you on the other front that we need to know why and how this condition occurred to begin with and if there is a defect here we need to address. Thanks,
> message = "Operation failed, diagnostics report: Hostsvc::osfs::CreateDirectory : Failed to create directory vm-27637 (Cannot Create File)" looks like osfs namespace directory creation is ... See more...
> message = "Operation failed, diagnostics report: Hostsvc::osfs::CreateDirectory : Failed to create directory vm-27637 (Cannot Create File)" looks like osfs namespace directory creation is failing. either Zerto is calling into wrong routine or our osfs dir creation is itself failing Looking at /var/log/osfsd.log might give more insights also am assuming that you can manually create vm dir from UI or using /usr/lib/vmware/osfs/bin/osfs-mkdir Thanks
No, we don't support this for shared controller settings as of today. Thanks,
you are using Vsphere Client and not NextGen vSphere webClient. hence the difference if you use vSphere client the menus will show-up in after you create and go to VM edit properties. editing... See more...
you are using Vsphere Client and not NextGen vSphere webClient. hence the difference if you use vSphere client the menus will show-up in after you create and go to VM edit properties. editing virtual machine properties -> Hardware -> SCSI controller -> SCSI controller type Thanks
Yes, AFAICT this is supported configuration. i don't know whether we explicitly called this out though... you can check this link for network design guide... http://www.vmware.com/files/pd... See more...
Yes, AFAICT this is supported configuration. i don't know whether we explicitly called this out though... you can check this link for network design guide... http://www.vmware.com/files/pdf/products/vsan/VMware-Virtual-SAN-Network-Design-Guide.pdf Thanks,
The problem seems to be double fault has occurred. and your policy can only tolerate 1 meaning, both the RAIDO copies(atleast one in each) of the RAID-1 are in bad state. ( your vm storage polic... See more...
The problem seems to be double fault has occurred. and your policy can only tolerate 1 meaning, both the RAIDO copies(atleast one in each) of the RAID-1 are in bad state. ( your vm storage policy image confirms this) you should check why the other RAID0 component was down. this is from a different spinning disk (disk UUID can be found in the vm storage policy image) Thanks,
can you provide screenshot image of what middle portion you are referring to ? Thanks,
Thanks Ahmad. good to know you were able to resolve the issue
which version of VSAN product you are using. VSAN 6.0 ? There are limited statistics for VSAN available via ESXTOP   (client/owner/CompMgr)|Read/s,|MB Read/s, AVGLat,SDLAT similar for Writes, ... See more...
which version of VSAN product you are using. VSAN 6.0 ? There are limited statistics for VSAN available via ESXTOP   (client/owner/CompMgr)|Read/s,|MB Read/s, AVGLat,SDLAT similar for Writes, RecoveryWrites) Start ESXTOP and press 'x'. if you want to see all the fields currently available press "fF" and select the fields(abcd) > Do you know if there is any manner to view vSAN metrics such as % dirty cache or flush rate? best way is to run vsan observer. its actually straight forward to run the observer by logging into cloudvm and running via RVC cmds Thanks,
> A customer require separate datastore, how can we accommodate two datastore using VSAN can we know what is the main reason/usecase for this ? Thanks,
> What is the best way to setup shared storage? > 1. Add more hard drives to server? > 2. Just buy a second server? You have two options: A. Setup VSAN. you will need to setup another ne... See more...
> What is the best way to setup shared storage? > 1. Add more hard drives to server? > 2. Just buy a second server? You have two options: A. Setup VSAN. you will need to setup another nested esxi server. follow this link http://www.virtuallyghetto.com/2013/09/how-to-quickly-setup-and-test-vmware.html B. for you existing 2 esxi servers, you can add shared storage which would come from your physical server from your physical server, power off nested esxi servers. i. edit virtual machine settings of one nested esxi server VM from UI and add a New device "SCSI controller" from select menu ii. Expand this newly added SCSI controller and choose the SCSI Bus Sharing option to "Virtual". Meaning Virtual disks can be shared between virtual machines on the same server iii. After this add a harddisk from the New device-> select drop down menu. Expand the newly  Newly added "Hard disk" and under "Virtual device Node" selection box  choose the "New SCSI controller" added. from the other nested esxi server, repeat the above steps (i & ii) and then select "Existing Hard Disk" option from the "New device -> select" drop down menu and from browse menu choose the virtual disk added in step (iii) Then power-on both nested esxi server VMs. you will be able to see the added harddisk shared between two nested esxi servers Thanks,
In 5.5 We support Cross-Host Storage vMotion,  which allows you to move **Powered On** VMs from one unshared datastore to another across hosts For cold migration, such has in your case you don... See more...
In 5.5 We support Cross-Host Storage vMotion,  which allows you to move **Powered On** VMs from one unshared datastore to another across hosts For cold migration, such has in your case you don't need this either and it should work. you need to choose "Change both host and datastore" option under "Migration Type" to actually move the VM Migrating Virtual Machines in the vSphere Web Client Thanks,
to add to what others have already covered in detail i do this on almost every major build in my internal test environment and it holds up fine, only thing is to make sure custom vCenter se... See more...
to add to what others have already covered in detail i do this on almost every major build in my internal test environment and it holds up fine, only thing is to make sure custom vCenter settings if any are re-added back to newer vCenter there are few additional things outside of what already been mentioned by folks here Its more of my observations and best practices rather than anything else... a. Before migration, collect/record the VM policy settings. and apply them after successful vCenter Swapping ( there should be some scripts to do this today. but not entirely automated/UI driven mechanism exists today...) I use vsan.recover_spbm rvc cmd b. also record/save any specific vCenter dependent/specific configurations so you can reapply them on newer vCenter c. Shutdown the Old vCenter server d. Always add hosts to root of the datastore on the newer vCenter. Then move them over to newer vsan cluster e. Check All VSAN Storage providers are registered  and Online. ( Vcenter host -> Manage -> Storage Providers section) ( Currently there is an issue out here that the first moved in host will not have Storage provider registered). You need to click on the toolbar "Synchronizes all Virtual SAN Storage providers with the current state of the environment". f. use vsan.recover_spbm rvc command and re-create the vsan policies and apply them to the respective VMs. g. if there were any VM templates before, you will have to re-add them to the new vCenter Thanks,
did your issue get resolved ? either the former comment on the network partitions or the disks from the CMMDs entry is false might be causing this. you can check this by this following comm... See more...
did your issue get resolved ? either the former comment on the network partitions or the disks from the CMMDs entry is false might be causing this. you can check this by this following command on each esxi host and see all the disks shows in CMMDS: true. # esxcli vsan storage list Used by this host: true    In CMMDS: false  <===== issue where the disks is not participating in vSAN storage. also check Re: vSAN weirdness.....Policy ? Thanks
you can also check by login to VC run the following rvc cmd > vsan.disks_stats 1/<datacenter>/computers/<vsancluster> this will give you details on all the disks used and health status ... See more...
you can also check by login to VC run the following rvc cmd > vsan.disks_stats 1/<datacenter>/computers/<vsancluster> this will give you details on all the disks used and health status of the vsan cluster Thanks,
this seems like only two hosts are part of the vsan cluster. can you confirm this by looking at vsan cluster -> Mange -> Disk Management -> { look at the column for Network partition} A... See more...
this seems like only two hosts are part of the vsan cluster. can you confirm this by looking at vsan cluster -> Mange -> Disk Management -> { look at the column for Network partition} All 3 hosts should be in the same group you can also check by running esxcli vsan cluster info on the host Thanks,