I also use MS Virtual Server at home (it is free), and VMWare ESX for work. (6.3 P22 Windows 2003)
Some key points to consider, is you MUST have knowledge of "Performance Tuning in Virtual Environments", the major bottle necks is not the CPU or Memory (faster and more is always best right!), however in the NETWORK Configurations... You must remember that for fail-over, etc that all NIC's are allocated to a BOND (Multiple Physical to one Virtual) and then the BOND is allocated (Attached) to the Virtual Server(s). Also remember the GIG-E full/auto-configuration issue... You MUST use a bunch of fore-thought to the allocation of these BONDS to the systems. We had terrible performance on ESX, until I (not the NT / ESX Administrators) got in and figured out that they had ONE BOND that was allocated to Remedy-Production Server and the Business Objects broadcast scheduler/server and one other 'heavy network' server... Well, as I say DDUUHH RIGHT! As soon as we reconfigured the three largest systems, POOF Screamed faster than the older physical hardware did. One other 'trick' is to create a VIRTUAL NIC, to connect your Server to the Database. Although this does have fail over restrictions (both VM's must be moved to another same-box-configuration)... As to "not officially supported", there are many things BMC (Remedy) does not "officially support" but in fact works OK, such as Fail Over Microsoft Clusters... (not that I suggest this any-longer, go VM!) You administrators can easily 'clone' a system into a new environment (for load ballencing), so you only patch ONE system, then "Clone & Configure"... Speaking of patching (Binaries, not application unfortunately), you can clone prod to a test, patch and test, then clone forward again. Total outage is very short, expecially in vload ballenced-virtual-ized environments. HTH Robert Molenda On Feb 3, 2008 8:19 AM, Jason <[EMAIL PROTECTED]> wrote: > ** I've run both ms virtual server and vmware with 6.3 and 7.01. A good > server with a dedicated NIC, multiple processors, and a few Gig's of RAM > will work for a smaller environment on 6.3. Just be prepared to throw A > LOT more hardware at it if you upgrade to 7 or have a lot of users and data. > > > Jason > > ----- Original Message ---- > From: Steven Pataray <[EMAIL PROTECTED]> > To: arslist@ARSLIST.ORG > Sent: Friday, February 1, 2008 12:22:47 PM > Subject: Virtualizing Remedy > > ** Our company is starting to get heavy on creating Virtual Servers but > none are production worthy yet because of the hardware on the physical > server. How close are other companies getting where Virtualization for > production machines are a reality? We are using Microsoft Virtual Servers at > work but at home I play with Vmware products IMHO is better. I'd really like > to get to the point where I can run a production Remedy server on a Virtual > server so Disaster Recovery is as quick and cheap as a copy/paste. Or an > production installation is as easy a download. > > Steve > > AR Server: 6.03.00 patch 023 > Mid-Tier Patch 21 > Oracle 10gR1 > HelpDesk 6.03 > > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ > > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
