irsprint84 (22nd January 2011)
We have a script that bassically Shuts down the VM Server then exports to backup, for backing up them restarts the Server all run on a schedule. If I want to Export a Snapshot I created I just Right click on the Snap shot and Export as long as where your exporting it to is mapped to your machine say NAS box or Terrastation you just select your location. We don't use any backup software.
I use Shadow copy setup to the Terrastation to do user araes and shared areas backups and usually evey Half Term run an NT backup to backup user data and shared areas as due to the restrictions on shadow copy number of backups.
irsprint84 (22nd January 2011)
My servers have to be up 24/7 so couldnt do that! but can you purposely run the snapshot from start to the NAS without having ot snapshot to the drive you want to snap shot?
irsprint84 (23rd January 2011)
There are many issues raised in this thread but very few actually addressed. To pick just one; Nobody seem to have mentioned the inability of Hyper-V to do memory over commit. The whole concept of hot migration of VM on host failure is meaningless in Hype-V unless you have hosts with double the memory allocated for VMs which seems a huge waste of resources. As for the implementation of clustered storage.. not the best in the world. I do have to say the product is improving and we do use a couple of refactored ESXs as Hyper-V servers with "clustered storage" for some of our Terminal servers, but at this stage I would not put anything really important on them. Until a time comes (and I am sure it will) when it does what VMWare does so well, my money stays with VMWare. Sorry have very limited experience of XEN so cannot really comment.
You are obviously going through troubled times and have had issues with VMWare in the past. As for the "fruit cake" analogy... that's probably about right for me. As for the HP issues, well you only have to read the VMWare forums about HP to see that they make uncomfortable bedfellows.
Last edited by Dave_O; 23rd January 2011 at 08:33 PM.
In my last job we implemented VM Ware on ESXi on 7 IBM hosts. It did everything we needed it to do and more. By all means it is not cheap but in my opinion it was worth the money. Never had any issues with it.
In my new job just bought 2 IBM servers and VM Ware ESXi again. If I didnt like it I would have looked for something else.
Not a huge fan of M$ to be fair, things are either over engineered, or appear to be an afterthought. Like the fact the Server Core which aims to match *nix versions by having a non GUI version, but Server Core has to start a GUI to run the CLI!
I was just going to post an identical thread but now I can just jump in and reply
When I think about the entire package the platform we choose will impact on other decisions as well. Looking at Hyper-V R2 and VMWare there’s a key areas I’m looking at…
• VMWare is obviously the more mature platform and was my initial choice just based on the fact it’s the recognised best-of-breed product for most people
• From discussions at BETT with techs other colleges there do seem to be more people putting faith in Hyper-V, especially since the R2 release
The main features that affect us would probably be…
• Memory overcommit, if we go Hyper-V we need to make sure any host has enough RAM to take the VMs from any other host as it can’t do VMWare-style RAM overcommit. Note: this feature seems to be coming in R2 SP1
Windows Server 2008 R2 SP1 Beta
• NIC teaming seems to be a bit of a worry on Hyper-V as it’s not officially supported (?) and seems to be down to how well the NIC drivers are working. We’re also going down the VLAN route so we can consolidate our networks so need to check how well a teamed \ VLAN tagged configuration works in Hyper-V.
If using Hyper-V how many NICs have you got going back to the core switch per host? Surely you need minimum 2 over two separate network cards to get any kind of redundancy and tbh I'd imagine more like 4 would be safe i.e. 2 x dual port NICs teamed to give bandwidth and redundancy.
• Hyper-V CSVs seem to work OK but don’t look quite as robust as VMFS, should do the job though
• Live Migration on Hyper-V is working OK in my test environment, one restriction is that only one live migration can be taking place at any one time compared to VMWare allowing multiple migrations but don’t think that’s a major issue for us
• Hyper-V won’t support Linux host OS unless we Enterprise Linux distributions, not ideal as we do use a few Linux boxes for some open-source apps
• OS patching; I can imagine Hyper-V will require patches to the underlying OS compared to VMWare so I guess that links in with the migration and stability questions above
• If we go down the Hyper-V route we can use DPM 2010 to backup via the VMs, software is basically free for us under Campus License with minimal cost on the agents
• If we go VMWare we could still use DPM but it would have to be via agents installed on the host. The other option would be something like Veeam, which seems to be quite well regarded. We currently have Backup Exec but looking at the options we’re wondering if it’s worth the money we spend on it each year. DPM does seem to be either loved or hated by people at the moment so would be interested to hear from anyone using it.
The future \ VDI
This is where I lean towards Hyper-V. From the discussions we had in December there’s still some way to go with VDI as a complete solution but we have a few rooms where it could do a job for us (student public use machines etc) and with Microsoft we’ll basically get those features for free. What with the developments they’ve made with RemoteFX I think MS might get ahead of View on this one.
So what I’m wondering is that if you didn’t have any virtual infrastructure in place and based on the current marketplace, pricing, features etc which would you go for? I wonder if my reasons for choosing VMWare are based on looking backwards at what it’s done whereas the reasoning for Hyper-V seem to be looking forwards to new solutions.
My head says VMWare but money-wise says Hyper-V will allow me to get my wireless project with the money I save!
A very comprehensive and measured post. I don't care what they say about Essex and the South , you've got my vote.
GShaw, that's a great analysis and after spending some time reading everyones response is the way I am swaying as well.
Thank you to everyone who replied to this thread, it certainly opened my eyes to some of the additional features out there.
Well it's not in the supported OS list so I guess it's a case of "you can do it but if it breaks it's not our problem"
Windows Server 2008 R2: Virtualization with Hyper-V: Supported Guest OS
they do say "other OS may work" so if you can get something going and seemingly working OK then fair do's. Might be OK for something only IT use like a Nagios install or something along those lines but personally I wouldn't want to run anything mission critical in an unsupported configuration...
Some other stuff:
AFIK hyperv with linux only supports 1 vcpu. Windows 1,2 or 4.
VMware supports 1 through 8 vcpu
Also hyper v isnt getting memory overcommit in sp1. Its getting dynamic memory. You set a startup ram and a maximum and thats it.
Theres no DRS in hyperv either.
Btw thanks for the comments Dave_O \ Tricky_Dicky
Interesting info about Dynamic Memory, I thought it would be better than that but I'm not surprised if it's a bit of a bodge. My real concern is the teaming issues, has anyone done it, either successfully or with issues?
Last edited by gshaw; 24th January 2011 at 12:42 PM.
Last edited by Dave_O; 25th January 2011 at 04:16 PM.
There are currently 1 users browsing this thread. (0 members and 1 guests)