The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

VMWare - Call me thick


  • Subject: VMWare - Call me thick
  • From: "Neil Wrightson" <neilw@xxxxxxxxxx>
  • Date: Mon, 5 Jul 2010 19:50:36 +1000

Hi All,

I read with great interest "Martyn Wendon's Four Nodes"
In here he mentions VMWare (which I've heard of before) and was thinking
this would be something I would like to implement.
My HA system as it stands has two PC's. A WHS (19" 2RU Box) and a XP
(19"
4RU Box) with Misterhouse, xAP, xPL on it.
I'm looking at reducing this back to a single PC, probably the (19"
4RU
Box).
They both have Digi 8 Port serial cards for the various HA interface bit's
and pieces.

I also have another 8 port Geovision (19" 4RU Box) that is not doing
anything.

My understanding of the VMWare, is that I can create many virtual machines
that can reside inside the one box.
These images, once setup, can be transferred between PC box's. So if the
4RU
box died, they could be transferred to the 2RU box etc.

So without having to re-create the WHS box, I can make an image as it
stands
and transfer it to the other box as a virtual machine?
If WHS works with VMWare, how does WHS & VMWare handle the way WHS
utilizes
the many hard disks into a single volume?
Does the WHS backups of client PC's still work?




Now for the thick part.
I'm looking on the VMWare website and it just isn't clear to me, what I
need
to download (and possibly buy).




Regards,

Neil Wrightson.




[Non-text portions of this message have been removed]



------------------------------------

<*> Join the Automated Home Forums
http://www.automatedhome.co.uk/vbulletin/


UKHA_D Main Index | UKHA_D Thread Index | UKHA_D Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.