Setup: We have an environment that is heavily IO bound (we are reading hundreds of images on a web page and hundreds of connections at peak times). Our environment consists of 4 physical servers and 4 virtual servers tied to a load balancer. We are seeing the following error on ONLY our virtual servers when under heavy traffic:
The specified network name is no longer available.
The network name that the error is referring to is a UNC path (\\server01\images\blahblah.jpg) The RAM on the physical vs. the virtual servers is similar. Physical and virtual servers have 8GB main memory with a 2GB page.
Question: Has anyone run into this error before? This is ONLY happening on our virtual servers. We have since taken the virtual servers out of the load balancing cluster and error has not been seen since, even under the same load during peak times. Could this be a limitation of the virtual environment that only so many file handles can be open at once? or would this point more towards a network saturation?