The firm's choice to go with a Microsoft Hyper-V Server environment started six years ago. This was when Microsoft acquired Connectix, which later became Virtual PC, Virtual Server and finally Hyper-V.
"At that time, we had joint ventures with Microsoft and Unisys to do testing on the Unisys ES7000," Lui says. "We found the virtualization software was not scalable enough as it was limited to only using one CPU. So we put it aside.
"We were really looking to increase utilization and consolidation," he adds. "So we were exploring different types of technology. Through a nondisclosure agreement with Microsoft, we knew that they had a good strategy for virtualization.
"Since we already were running a Microsoft platform, that gave us the best cost of ownership," he says. "That's why we picked the Hyper-V product above any others."
"We tested other solutions, but they did not perform to our satisfaction," Sorenson says. "The same applications we tested in Hyper-V showed better performance and met our application performance requirements."
"The beauty of Hyper-V is that you have the same [virtual] hardware all over the place," Snater adds. "So you don't have to find different drivers for a variety of servers. And you don't have to find different products to support the applications. That's a big win in time savings and troubleshooting."
But why go back at all? Business needs change and demand for application size changes. And the firm may need more flexibility in the future.
"If a developer doesn't support virtual server and they want us to reproduce an application error, you may have to be able to put it on a physical box again without reinstalling everything," Snater says.
Third-party vendors do offer a way to go back to physical servers. However, it's at an additional cost. Smead has acquired a few licenses of the app but has not used them.
"To be honest, you're taking some risk in moving some non-Hyper-V supported applications over to Hyper-V," says Snater. "But we tested them and they run. And we haven't experienced issues.
"We have a process server that determines whether an application can be virtualized," he adds. "So we use a third-party V2P as a potential fallback."
The company has also taken the leap to virtualize its Logan, Ohio disaster-recovery site. "We know that disaster recovery is much easier and faster with a virtualized system," Lui notes.
By day, the disaster-recovery site is a development test system. But in the event that a disaster does occur, the company can enable the system for disaster-recovery mode and activate the production copy whether it's a database or applications.
"We look at this strategy as a method for efficiency," Sorenson adds.
"It enables a copy of our production virtual machines at our DR site. "Our goal would be to not have to have completely separate parallel systems and minimize that complexity," he adds. "We are replicating our database every day over there so we have a disaster system ready any time."