Vista - Last hope to get solution provided real Hyper-V high availability.

Hi,

I’m building High Available solution using Hyper-V and Microsoft Fail over
cluster. My target is to double all hardware to eliminate single point of
failure. I know how to provide iSCSI network redundancy, heart beat network
redundancy. I also know how to set up firewall redundancy.

Unfortunately weak point in my plan is public network redundancy. I tried to
find any solution for eliminating single switch and NIC point of failure (as
far as I know I can use teaming due not compatibility with Hyper-V issue). In
my opinion it is quite probable that one NIC or switch will be down
(especially that I met Cisco switch completely stopped to work). Only advice
I’ve got is to provide second, stand bay network and when I will find NIC or
switch be down I can manually change virtual switch to another adapter
(unfortunately in my case it has to be automatic process).

However I have still hope someone can give me answer for this question.

Best Regards

No pretty solution, but it's fairly simple to create a script that runs and
checks if the network is up and working, and if not, switch it over.
Depending on how often you ping, and how many failures you wait for before
switching, the whole process could be quite quick. And automatic. No, I
don't like it. Yes, I understand what you're asking for, but it isn't
possible yet because of the teaming issues. This, at least, would not
require manual intervention. And could, of course, include such niceties as
automatic notification, etc.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel

"Piotr" <Piotr@xxxxxx> wrote in message
news:C65F0193-D13F-4753-A63F-A71416617712@xxxxxx

I don’t like this idea either. However if I have no choice it is better than
nothing. Could you give me idea how to do this please or how to find similar
script (unfortunately I’m not scripting guy)? Do you mean script on parent on
child partition?
Regards

A good starting point is the Technet Script Center. There's lots of
scripting starting points there. You can use VBScript or Hyper-V as your
base language. Though I suspect you'll have to do either some serious WMI to
get it done.

If you use SCVMM 2008 (about to RTM in the next 30 days), you've got a huge
head start on PowerShell environment, since it let's you do a process and
save off the Posh script for it.

Where you run your scripts will depend on how you set up your environment
and what the actual requirements are, and the scripting environment
available in them. My guess is you'll be running on the parent, however,
predominently.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel

"Piotr" <Piotr@xxxxxx> wrote in message
news:8EF46B2C-D7B5-43AD-92DA-97228A4B770E@xxxxxx