Does ESXi 5.5 Update 1 NFS issue affect vPower NFS?

[keithlammers]

We were planning to upgrade our hosts to ESXi 5.5 Update 1 next week, but I came across the following VMware KB article regarding NFS disconnects: http://kb.vmware.com/kb/2076392

Has anyone upgraded to 5.5 Update 1 yet, and if so, have you tested a Veeam Instant Recovery to see if it still works fine after the upgrade?

Thanks!

[Vitaliy S.]

Since vPower NFS datastore which is used in Instant VM recovery process is a regular NFS datastore, it can potentially be affected by this behavior as well. I would hold off the upgrade to this update, unless there is a strong reason to do so. On the other hand, assuming that Instant VM Recovery is not used very often (only during DR situation), it shouldn't be critical to jump on this vSphere update level.

[keithlammers]

Thanks Vitaliy! We don't use Instant Recovery often, but definitely don't want to be caught out by the issue if for some reason we do need to use it for disaster recovery before VMware patches the issue. Guess we'll stick with 5.5 GA for now

[connelp]

I am in a similar position too, though I am currently running ESXi 5.0 U3. Obviously I want to upgrade, but not if there are known problems!

It would be very useful if Gostev could mention in his digest (which is an excellent resource BTW) when VMWare have fixed this problem.

[Gostev]

OK, I will try to remember to do this.

[connelp]

Sorry to bump this, but is anyone aware if this is still a problem and has anyone spoken to VMWare about when they expect to fix it?

[Gostev]

I have not heard of any news, but I would expect VMware to treat this issue as critical, considering they probably have at least about 20% of their customer base using NFS for production storage. Think half of all NetApp deployments in the world alone!

[dellock6]

Still no official news from VMware, the bug is still out in the wild. We will for sure update this thread once the solution will be available.
For now, still the only real solutions are to not update, or to revert to previous ESXi versions if they were already updated, there is no problem in keeping the updated vCenter together with them. obviously this becomes more complex if some of the features of U1 are needed, mainly VSAN, but it's unlikely for an environment to have both VSAN and a classic NFS storage, if not during a migration period...

[lp@albersdruck.de]

There seems to be a patch available now:
http://kb.vmware.com/selfservice/micros ... Id=2077360

[dellock6]

Yes Lars, you anticipated me in updating the thread
Seems from the first feedbacks all over internet the patch is working, so please guys consider it also to fix vPower NFS connection problems with 5.5u1.

Luca.