I've been running Destiny virtualized on ESX for serveral months. Not a single issue. JR
_____ From: John Hornbuckle [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 22, 2008 1:33 PM To: NT System Admin Issues Subject: RE: Will it *really* not work virtualized? This is Follett's "Destiny" product. From: Jon Harris [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 22, 2008 2:30 PM To: NT System Admin Issues Subject: Re: Will it *really* not work virtualized? I am getting a 404 on that page what is the name of the product. I had the Winnebago card catalogue system running on a virtual machine for about a year with no issues. Jon On Tue, Jul 22, 2008 at 2:25 PM, John Hornbuckle <[EMAIL PROTECTED]> wrote: It's a program to use in school libraries for checking books in and out. It uses an SQL database (http://www.fsc.follett.com/_files/fsc/secured/system_requirements/Dest%20Sc hool%20sys%20reqs%2010685A%20PDF%20print%207_08a%20(2).pdf). We're a small district with small schools, and no app we've ever run on a server has come anywhere close to fully utilizing the hardware. That's one of the reasons I want to virtualize more. If the app will run on an XP "server" with a Pentium 4 processor, I can't imagine that it would be overly demanding. But they do say they require RAID 1 or 5, so they must be counting on a fair amount of I/O activity. But I wonder, what exactly is "high" I/O when it comes to figuring out if something will run okay on a virtual server? From: Sherry Abercrombie [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 22, 2008 2:14 PM To: NT System Admin Issues Subject: Re: Will it *really* not work virtualized? Why would a product not work on a virtual server, well, one that is high I/O, as in a database server would possibly not work. What application specifically are you looking at that says this? We've used virtual servers for probably 5 years now, and we've always taken the approach that we will try it on a virtual server and if it doesn't work, then go to physical. So far, we're doing really good with that approach. 99% of what we've tried on a virtual server has worked. Now to counter that, we have always looked at what the application will be doing, evaluated the requirements and load, and made the decision on whether or not it's a good candidate for virtualization or not a good candidate for virtualization. Now with that said, I do have a caveat, I've never used Hyper-V and probably will never use it, we've been VMWare since we started with virtual server, first GSX now the latest release of ESX. So, I can't say how Hyper-V utilizes system resources compared to ESX..... On 7/22/08, John Hornbuckle <[EMAIL PROTECTED]> wrote: I was looking over the system requirements for a particular piece of software we're looking at purchasing, and I noticed that it specifically says it has to be on a physical (non-virtual) machine. Now, this software doesn't have any special hardware requirements. Processor requirements are modest, as are requirements for RAM and storage space. And yet, the requirements explicitly say, "Microsoft Windows Server 2008 Standard or Enterprise without Hyper-V" (if Server 2008 is the OS--it also supports Server 2003, XP, or Vista as the server OS). As I've mentioned before, I'm brand new to server virtualization. I'm playing with Hyper-V right now for the first time. So, I'm sure I'm missing something. Why, exactly, would a product like this not work on a virtual server? John Hornbuckle MIS Department Taylor County School District 318 North Clark Street Perry, FL 32347 www.taylor.k12.fl.us <http://www.taylor.k12.fl.us/> ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ -- Sherry Abercrombie "Any sufficiently advanced technology is indistinguishable from magic." Arthur C. Clarke ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
