+ Post New Thread
Page 2 of 2 FirstFirst 12
Results 16 to 21 of 21
General Chat Thread, How can I use virtualization in my new network in General; Originally Posted by superfletch I feel like I should know more about this conf', where, when, and how do we ...
  1. #16

    Ric_'s Avatar
    Join Date
    Jun 2005
    Location
    London
    Posts
    7,599
    Thank Post
    109
    Thanked 765 Times in 596 Posts
    Rep Power
    181
    Quote Originally Posted by superfletch View Post
    I feel like I should know more about this conf', where, when, and how do we book?

    Is the whole conf' aimed at virtualisation tech or just the section you're doing?

    Cheers,
    Only my section is on virtualisation... there will be other stuff too.

    By the end of the Easter break we should have the full details for you all and a lovely booking form - this will give you over a month to work out travel arrangements and accomodation.

  2. #17
    DMcCoy's Avatar
    Join Date
    Oct 2005
    Location
    Isle of Wight
    Posts
    3,462
    Thank Post
    10
    Thanked 496 Times in 436 Posts
    Rep Power
    113
    Quote Originally Posted by Ric_ View Post
    I will be giving an overview of virtualisation technologies and its uses at the May conference - not long to go now

    Although I would agree with tmcd35 about consolidation, 'high availability' (HA) is also a top reason for virtualising servers. For instance, your current DC explodes in a ball of flames... you need to order a new server, set it up, test it and then make it live. With virtualisation, you automagically failover to a second box.
    We don't actually use HA, having only a VMware standard+vmotion license.

    There are lots of other reasons though:

    Templates
    Hardware independence for servers
    Server Maintenance (bios updates and patches etc)
    Multiple OS types on a single machine
    Important roles spread out to reduce impact of patching/reboots of VMs

    To instantly fail over (not just automatically start on another server) without service interruption you would still need something like MS clustering etc.

    I've been reading up on Microsoft's solution to the lack of a cluster file system for R2, and what I've read makes me highly sceptical about R2s Hyper-V implementation, which is a shame as I would like to move to it when I finally have servers that support it!

  3. #18

    Theblacksheep's Avatar
    Join Date
    Feb 2008
    Location
    In a house.
    Posts
    1,935
    Thank Post
    138
    Thanked 290 Times in 210 Posts
    Rep Power
    193
    Quote Originally Posted by DMcCoy View Post
    To instantly fail over (not just automatically start on another server) without service interruption you would still need something like MS clustering etc.

    I've been reading up on Microsoft's solution to the lack of a cluster file system for R2, and what I've read makes me highly sceptical about R2s Hyper-V implementation, which is a shame as I would like to move to it when I finally have servers that support it!
    In ESX 4 (which I think is due to release in two weeks), hey, people are talking about MS features that wont be available for a year, so a few weeks is also ok! There a new feature called VM lockstep where two VMs run at the same time, if one fails the other becomes the live copy. I'm not sure at which level the service get introduced though.

    I'd like to add that DRS and power managment is another quite important VM feature, not top of the list, that is missing from the MS implemention. Dynamic filtering of where to start VMs in the event of failure or in the case of hot cloning for VDIs, starting and moving the VMs around host depending on load. Even moving VMs to one host at night when load is low and shutting down other hosts for power saving/maintenance.

    Moving storage while the machines are live is also a pretty good feature.

    Transparent page file sharing and ISO instancing are another two examples that are not too important when you dont have it, but add a little extra to server and space consolidation when you do.



    Yet another disk died on our RM exchange server the other night, so I P2V it... increased the C drive space from 8GB (pathetic) to 16 and it was running again in 6 hours.
    Last edited by Theblacksheep; 8th April 2009 at 12:31 PM.

  4. #19
    superfletch's Avatar
    Join Date
    Nov 2007
    Location
    South
    Posts
    434
    Thank Post
    146
    Thanked 77 Times in 61 Posts
    Rep Power
    31
    Quote Originally Posted by Ric_ View Post
    By the end of the Easter break we should have the full details for you all and a lovely booking form - this will give you over a month to work out travel arrangements and accomodation.
    Any info on those dates available yet?

    Cheers,

  5. #20

    SpuffMonkey's Avatar
    Join Date
    Jul 2005
    Posts
    2,240
    Thank Post
    55
    Thanked 278 Times in 186 Posts
    Rep Power
    134
    Quote Originally Posted by tmcd35 View Post

    In both cases both hosts need access to the volume the VM is stored on - either NFS/SMB share or SAN LUN via a clustered file system.
    As someone who is just about to dip their toe in this somewhat muddy pond - what's considered the best way of locating the VMs - do you run ESXi on the physical server and keep the VMs on the SAN? Or run ESXi & the VMs on the physical server, but locate your data/backups on the SAN? Be interested to hear what people do.

  6. #21

    tmcd35's Avatar
    Join Date
    Jul 2005
    Location
    Norfolk
    Posts
    5,691
    Thank Post
    851
    Thanked 899 Times in 744 Posts
    Blog Entries
    9
    Rep Power
    329
    The VM's belong on the SAN. The VMFS formatted LUN that the VM's are stored on should be visable by all of your ESX/ESXi servers. This way, If one of the servers are taken out of action for a while, all the VM's normally controlled by that server can be quickly and easily restarted on any other server, if memory and processor allocation allow.

    For this reason I don't normally recommend, in day to day use, provisioning more than <number of ESX/ESXi Servers - 1>/<number of ESX/ESXi servers> of the total capacity of each server.

    So if you have 3 servers - you'll use 2/3rds of their total capacity. If you have 4 servers it'd be 3/4 of the servers capacity used. This way if 1 server goes down you are more than likely to have the space accross the other servers to run the effected VM's.

SHARE:
+ Post New Thread
Page 2 of 2 FirstFirst 12

Similar Threads

  1. Server Virtualization or Not to Server Virtualization
    By IanT in forum Wireless Networks
    Replies: 11
    Last Post: 29th January 2009, 02:09 PM
  2. Virtualization
    By Hightower in forum Thin Client and Virtual Machines
    Replies: 28
    Last Post: 22nd September 2008, 04:35 PM
  3. For anyone interested in Virtualization
    By somabc in forum How do you do....it?
    Replies: 3
    Last Post: 5th August 2008, 12:27 PM
  4. Virtualization explained
    By KWestos in forum Thin Client and Virtual Machines
    Replies: 9
    Last Post: 14th July 2008, 10:33 AM
  5. New Forum for Virtualization
    By JamesC in forum Comments and Suggestions
    Replies: 3
    Last Post: 20th February 2008, 03:10 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •