Quantcast
Channel: VMware Communities: Message List - vSphere™ Storage
Viewing all 5826 articles
Browse latest View live

where to buy a speedometer?

$
0
0
Greetings everyone,
Just arrived here and found this forum quite good, 
so I wanna know that from where I can buy sphygmomanometer?
Actually I need it for my home, I saw some good digital and manual on https://www.reecoupons.com but I dont know which one is better to buy.
Should I buy a digital or manual?
Pl suggest me waiting for your replies.

Re:where to buy a speedometer?

$
0
0
Greetings everyone,
Just arrived here and found this forum quite good, 
so I wanna know that from where I can buy sphygmomanometer?
Actually I need it for my home, I saw some good digital and manual on https://www.reecoupons.com but I dont know which one is better to buy.
Should I buy a digital or manual?
Pl suggest me waiting for your replies.

Re: Intel Optane 905P VS Samsung 983 ZET best performance for running many Virtual Machines in vSphere simultaneously

Help Removing Datastore

$
0
0

I have a datastore that i am trying to remove and it tells me there is a Virtual Machine that is referencing this datastore. However, when i look at the DS there are NO files listed.  Any help is appreciated.  Thanks

Re: Help Removing Datastore

$
0
0

Does any of the VM's have a reference to e.g. an ISO image that was stored on that datastore? If so, ste the VM's virtual CD-ROM drive to e.g. "Client-Device".

It may also be possible that a VM had with active snapshots had a reference to such a file at the time when the snapshot was created. In this case you need to delete the snapshot.

André

Re: Help Removing Datastore

$
0
0

Well there are no ISO files on that DS and never were.  I keep those on another.  As for the snapshot option, wouldn't the snapshot file show up on the DS?  There are absolutely no files on that DS and that is why i am confused.  I can search for snapshots but don't believe that i will find anything.  Thanks for the reply.

Re: Help Removing Datastore

$
0
0

Have you recently moved any VMs off that datastore? Maybe this reduces the VMs that need to be checked!?

Btw. what's the exact error message that you get? Just want to rule out that it's a HA heartbeat datastore that prevents you from removing the datastore.


André

Re: Help Removing Datastore

$
0
0

Well, Apparently i am blind.  There was a template pointing to it and it was coming from the other cluster.  My old storage is shared between both clusters and that is changing for that very reason.  Thanks for the help!!  really appreciate it.


ISCSI APD timeout issue in ESXi 6.7.0

$
0
0

Issue APD timeout issue in ESXi 6.7.0

 

Our setup:-

 

This is pre-prod setup with 4 ESXi servers backed by Windows ISCSI storage.

ISCSi data store  size is 10 TB( presented from Windows physical ISCSI server) and the same is presented to all the 4 ESXi servers.

 

When Im try to do storage vmotion of any big size VM from local datastore(600 GB VM) to ISCSI data store,it gets interrupted in the middle(I mean after 60 % of storage vmotion,esxi servers one by one one goes to not responding state because of APD situation),To solve this issue,we should take one by one ESXi reboot and happens frequently whenever we do storage vmotion.

 

See the logs below:-

 

2019-12-03T21:36:32.018Z: [APDCorrelator] 608631351756us: [vob.storage.apd.timeout] Device or filesystem with identifier [naa.604b53240003606301d5aa1ee87489b0] has entered the All Paths Down Timeout state after being in the All Paths Down state for 140 seconds. I/Os will now be fast failed. 2019-12-03T21:36:32.018Z: [APDCorrelator] 608633935712us:

 

 

[esx.problem.storage.apd.timeout] Device or filesystem with identifier [naa.604b53240003606301d5aa1ee87489b0] has entered the All Paths Down Timeout state after being in the All Paths Down state for 140 seconds. I/Os will now be fast failed. 2019-12-03T21:36:47.993Z: [iscsiCorrelator] 608647326769us: [vob.iscsi.target.async.event]

The target iqn.1991-05.com.microsoft:-mts-iscsi-win-lun3-target issued an async event for vmhba64 @ vmk1 with reason code 0000

 

To solve this issue,

 

1) We have increased the value of APD timeout to 300 seconds instead of 140 seconds (on all the ESXi hosts) Change Timeout Limits for Storage APD

2) We have disabled the "Delayed ACK" on all the 4 ESXi hosts    VMware Knowledge Base

 

After this above 2 parameters change,now it is stable for the last 12 hours and storage vmotion got completed without any issues.

 

Any other recommendations(with respect to APD time out value) is there from ESXi/ISCSI end ? please suggest.

 

Thanks,

Manivel R

Re: ISCSI APD timeout issue in ESXi 6.7.0

$
0
0

Just because I saw you configured the iSCSI as the storage, do not forget if you enable software iSCSI multipathing, you must consider to create 2 separate VMkernel port groups and connect one uplink to each of them. Also, you should bind each VMkernel network adapter to the software iSCSI adapter.

Re: ISCSI APD timeout issue in ESXi 6.7.0

$
0
0

Moderator: Moved to vSphere Storage

Re: ISCSI APD timeout issue in ESXi 6.7.0

$
0
0

Hi Amin.

Im using iscsi software storage adapter.

Before that I created one vmware vmkernel adapter and tagged with iscsi storage adapter.

My uplink is just one nic.

 

Thank you,

Manivel R

Re: vSphere 6.0 Web Client cannot browse Datastore files (but old VSphere thick client can)

$
0
0

Did you find a workaround?

 

I am having the same issue. I have checked with Chrome and Mozilla.

Re: Intel Optane 905P VS Samsung 983 ZET best performance for running many Virtual Machines in vSphere simultaneously

Improving Stun Times

$
0
0

VMware 6.0

Compellent SC5020 SAN connected with 10GB

VM Size 1.6TB

VM Workload: SQL

12 disks split among 3 paravirtual controllers

OS disk using LSI Logic SAS

 

Does anyone know if there is anything else we can do to increase performance for stun times? We are getting really good stun times but sometimes the stun times go up.

I pulled the stun times for the last 30 days for this VM and for the most part it's a tenth of a second or half a second but sometimes it increases to 1.5 seconds with the highest being at 1.9 seconds.

The average for the month is .59 seconds, I know these stun times are probably already in the "excellent" category but I would like to see if there are any tweaks to bring them down even further. especially the ones that creep up over a second.

 

I attached our report of stun times for this VM for the last 30 days in case anyone's interested.


Re: Improving Stun Times

$
0
0

Moderator: Moved to vSphere Storage

Re: Improving Stun Times

$
0
0

Stun times are heavily linked to underlying storage performance and that of the hypervisor as well, so unless you have some of that other data and have attempted some correlation, just a table of those times isn't enough to go on. And on that point, it would be better if you could paste that text in-line to your response (VMTN has an insert table feature). It's generally not safe for strangers on the Interwebs to be opening MS Office documents from other strangers.

 

I would begin by looking at your Compellent array and correlate the stun times with those metrics to see if you're getting a spike at the storage layer or what that storage says at all.

Re: Improving Stun Times

$
0
0

Thank you for your response.

 

My next step is to work with Dell Compellent support and see if we can correlate those times and IO performance. Just wanted to show the stun times list is already good and you are correct, on it's own they mean nothing. Hopefully it will spark a conversation with anyone that was trying to improve their environment as well.

Re: Improving Stun Times

$
0
0

I worked with Compellent support and they were unable to suggest anything either. The IO burst that happens during a snapshot is so insignificant and seems they only suggest following the best practices guide, which we already have.

Re: Improving Stun Times

$
0
0

What is the VMFS version used in your case?

 

thanks

G

Viewing all 5826 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>