Upgrading Hyper-V Server 2008R2 Cluster to 2012R2

I have a Hyper-V Server 2008R2 (free 'core' version) cluster that I would like to upgrade to Hyper-V Server 2012R2 (same 'core' version).  I found
this document that seems to outline the process, however I have the following questions...
Any reason this process won't work on the "core" version of Hyper-V.  i.e. "Microsoft Hyper-V Server 2008R2".  I currently have a 2-node 2008R2 HA cluster with "core" servers and am looking to migrate that cluster
to the "core" version of 2012R2.
Is there no way to do this "in place", meaning without a dedicated target server?  It seems like the process assumes you just have extra servers sitting around that can act as targets.  I suppose I could shuffle VMs off one cluster node,
evict that node from my current cluster, rebuild it with 2012R2 core, add it to a new cluster as the only node and carry on with the process outlined here?  Once all VMs are on the new "cluster" of one 2012R2 node, I would destroy the original
cluster, rebuild those machines with 2012R2 and add them as nodes to the new cluster?
Any reason the "Failover Cluster Manager" tool, version 6.1, I've been using to manage my 2008R2 environment won't work to do the migration?  Or are there new 2012 tools I need to have installed on my workstation.  Remember, since this
is the "core" version I can't manage anything from the server.
Thanks,
Todd

Here's an update on what happened...
The first VM that failed turned out had 1 snapshot, which I know is a no no, but I generally never snapshot servers so it didn't even occur to me to check.  So that's why the migrated VM wouldn't boot.  When I recreated the VM manually and pointed
to the VHD file it obviously didn't include the AVHD content so it booted the server into a 2 month old state.  That led to the domain problems since the AD server account password had changed sometime in the last 2 months.  I tried a bunch of fixes
but the only thing that finally worked was to remove the server from the domain and re-join.  Of course, that then broke Citrix, but that's getting off-topic.
The second VM that failed was because for some reason a CSV that it relied on was not migrated over and I didn't notice that in that in the report.  And then I couldn't find any way to bring that CSV in after the fact.  I re-ran the pre-migration
and it still didn't show it.  Of course this is my biggest volume at 800GB.  So I then re-mapped one of my old cluster nodes back to the LUN (after removing the new node), brought up the lost CSV, copied the VHD file on it to external media, brought
the old cluster down again, the new one up and was going to blow away that LUN and create it as a new CSV on the new cluster.  Of course, when I went to go create the CSV it showed my LUN available for storage and I just had to add it and all the data
was brought with it.  So 2 hours of copying for nothing!  I'm not at all sure what happened with this problem, but it seems either rebooting the old cluster node or the new one jarred things lose.
Just wanted to report back saying everything is going again.  And also to vent about how poor and riddled with pitfalls this migration is.  The snapshot issue is ridiculous, how hard would it be for the tool to check for that and then throw an
error in the migration report?
For anyone that needs to upgrade from 2008 to 2012, good luck!

Similar Messages

  • Upgrading hyper-v server 2008r2 free version to hyper-v server 2012r2 free version

    Hello, 
    I have a question, can I upgrade the software of hyper-v server 2008r2 free version to hyper-v server 2012r2 free version.
    I want to upgrade a exciting server so a in place upgrade, if yes do I have to worry about something? like shutting down vm's?
    thx in advance

    Hi,
    it's not possible to perform an inplace upgrade from Hyper-V server 2008R2 to Hyper-V server 2012
    You can find some more info
    here.
    You can export your Hyper-V guests, reinstall the machine with a fresh install and import them again.
    Hope this helps.

  • Can't Open Reports after upgrading to Windows Server 2008R2

    Since upgrading to Windows Server 2008R2, I am unable to use File > Open to browse my network for existing Crystal Reports.  I am able to access reports from my recent reports list.  If I use Windows Explorer to try to find/open an existing report file, I'm prompted for the installation disk.  Is this a known issue?  Thanks for your help.

    SP2 fully supports Windows 2008 Server, here's a link to the [platforms PDF|http://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/00225757-ab5c-2c10-c1a8-fb9f9f0f4ac2&overridelayout=true] file:
    As for permissions this is something you need to setup with Windows and file sharing.
    Thank you
    Don

  • Sql server 2008R2 cluster (active-passive) prerequistites

    Hi All,
    Please any one can help me in exact prerequisites for installing sql server 2008R2 cluster server(two node).
    Thanks in advance.
    Maheshwar Reddy

    Hi Please find the pre-requisites for SQL server cluster installation .
    Before Installing SQL cluster we need to have a Windows Cluster with required shared storage space and DTC Service configured in Windows
    Cluster.
    Be ready with the plan of where the SQL to be installed and where the Database, Log, Temp DB and Backup are to be stored.
    If you require SOP for this please share your mail id .i will send the same .

  • Setup test envrionment for windows server 2008r2 cluster + oracle failsafe

    Hi All,
    Would like to set up windows server 2008r2 cluster + oracle failsafe for testing purpose.
    Am new to this. I have a windows 7 desktop machine.
    Can i acheive it using virtual box or?
    Need your advise here.
    thanks!

    dbaing wrote:
    Hi All,
    Would like to set up windows server 2008r2 cluster + oracle failsafe for testing purpose.
    Am new to this. I have a windows 7 desktop machine.
    Can i acheive it using virtual box or?
    Need your advise here.
    thanks!http://www.oracle-base.com/articles/11g/oracle-db-11gr2-rac-installation-on-oel5-using-virtualbox.php

  • Upgrading from Windows Server 2008r2 to 2012r2

    We have an existing Windows Server 2008R2 which Crystal Reports delivering reports via our website. 
    On the Windows 2008 server, we used Crystal Reports version 2008.
    I am now updating my Windows Server to 2012, and because Crystal Reports 2008 does not work on this server, I am trying to use the latest version.  (I downloaded the trial -- once it works, I will purchase.)
    Below is the Web.config file I have on the 2008 server (and this works on the 2008 server
    <?xml version="1.0"?>
    <!--
        Note: As an alternative to hand editing this file you can use the
        web admin tool to configure settings for your application. Use
        the Website->Asp.Net Configuration option in Visual Studio.
        A full list of settings and comments can be found in
        machine.config.comments usually located in
        \Windows\Microsoft.Net\Framework\v2.x\Config
    -->
    <configuration>
        <appSettings>
            <add key="CrystalImageCleaner-AutoStart" value="true"/>
            <add key="CrystalImageCleaner-Sleep" value="60000"/>
            <add key="CrystalImageCleaner-Age" value="120000"/>
        </appSettings>
        <connectionStrings/>
        <system.web>
            <!--
                Set compilation debug="true" to insert debugging
                symbols into the compiled page. Because this
                affects performance, set this value to true only
                during development.
            -->
            <compilation debug="false">
                <assemblies>
                    <add assembly="CrystalDecisions.Web, Version=12.0.2000.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>
                    <add assembly="CrystalDecisions.Shared, Version=12.0.2000.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>
                    <add assembly="CrystalDecisions.ReportSource, Version=12.0.2000.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>
                    <add assembly="CrystalDecisions.Enterprise.Framework, Version=12.0.1100.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>
                    <add assembly="CrystalDecisions.Enterprise.Desktop.Report, Version=12.0.1100.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>
                    <add assembly="CrystalDecisions.ReportAppServer.Controllers, Version=12.0.1100.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>
                    <add assembly="CrystalDecisions.CrystalReports.Engine, Version=12.0.2000.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>
                    <add assembly="CrystalDecisions.Enterprise.InfoStore, Version=12.0.1100.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>
                    <add assembly="CrystalDecisions.Enterprise.Viewing.ReportSource, Version=12.0.1100.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/><add assembly="CrystalDecisions.ReportAppServer.ClientDoc, Version=12.0.1100.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/>
                    <add assembly="CrystalDecisions.ReportAppServer.CommonObjectModel, Version=12.0.1100.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>
                    <add assembly="CrystalDecisions.ReportAppServer.DataDefModel, Version=12.0.1100.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>
                    <add assembly="CrystalDecisions.ReportAppServer.ObjectFactory, Version=12.0.1100.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>
                    <add assembly="CrystalDecisions.ReportAppServer.ReportDefModel, Version=12.0.1100.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>
                    <add assembly="CrystalDecisions.CrystalReports.TemplateEngine, Version=12.0.1100.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/>
                    <add assembly="System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                    <add assembly="System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
                    <add assembly="System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                    <add assembly="System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                    <add assembly="System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
                    <add assembly="System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
                    <add assembly="System.Web.Services, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                    <add assembly="System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                    <add assembly="System.DirectoryServices.Protocols, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                    <add assembly="System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                    <add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                    <add assembly="System.ServiceProcess, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                    <add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
                    <add assembly="System.Web.RegularExpressions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
                    <add assembly="CrystalDecisions.Data.AdoDotNetInterop, Version=12.0.2000.0, Culture=neutral, PublicKeyToken=692FBEA5521E1304"/></assemblies></compilation>
            <!--
                The <authentication> section enables configuration
                of the security authentication mode used by
                ASP.NET to identify an incoming user.
            -->
            <authentication mode="Windows"/>
            <!--
                The <customErrors> section enables configuration
                of what to do if/when an unhandled error occurs
                during the execution of a request. Specifically,
                it enables developers to configure html error pages
                to be displayed in place of a error stack trace.
            <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
                <error statusCode="403" redirect="NoAccess.htm" />
                <error statusCode="404" redirect="FileNotFound.htm" />
            </customErrors>
            -->
            <httpHandlers><add verb="GET" path="CrystalImageHandler.aspx" type="CrystalDecisions.Web.CrystalImageHandler, CrystalDecisions.Web, Version=12.0.3700.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/><add verb="GET" path="CrystalImageHandler.aspx" type="CrystalDecisions.Web.CrystalImageHandler, CrystalDecisions.Web, Version=12.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/></httpHandlers></system.web>
    </configuration>
    What do I need to install and what changes to the web.config do I need to make to have my reports continue to display via my website?

    First, you need to download the new SDK - it's no longer available as part of the Crystal Reports install.
    To do this go here:  http://scn.sap.com/docs/DOC-7824.  Download and install the latest version of the "Install Executable" to get integration into Visual Studio.  The other installs are the runtime installs - select the appropriate runtime install for your environment.
    Now you have to upgrade your application to VS 2010 or newer.  There are some changes to the SDK, so you can't just replace the assemblies in your existing application's configuration.  DO NOT compile as "any CPU", you need to specifically target either x86 (32-bit runtime) or x64 (64-bit runtime).  If you target the 32-bit runtime (which will run on a 64-bit server!) and you're using ODBC, you'll need to create 32-bit ODBC connections on the server.  In any case, when working in VS, you'll need 32-bit ODBC connections for testing.
    -Dell

  • Error upgrading Hyper-V Server 2008 R2 to 2012: 0x80070490

    Hi everyone!
    As it is release day for Hyper-V Server 2012, I decided to go ahead and upgrade from Hyper-V Server 2008 R2.  However, I keep getting this error: 
    "Windows Setup cannot find a location to store temporary installation files.  To install Windows, make sure that a partition on your boot disk has at least 1198 megabytes (MB) of free space.
    Error code 0x80070490"
    I have over 20 gigs free on the boot volume, and tons more on my VHD volume, so I don't know why it's doing this.  I have shut down all VMs, there are no snapshots, nothing cluttering up my C: drive, and yes I've rebooted it several times.  I have
    also tried copying the installation DVD to a local volume and installing that way, but I keep getting the same error.  I know the quick solution would be to just format, reinstall clean, and pray that my VMs import into 2012 (which are already safely
    on another volume), but there has to be a reason this is happening.
    Any ideas?  :)  Thanks!

    Hello Vincent,
    I get the same error trying to upgrade my 2008R2 server to 2012. Here's my diskpart output for the partition (it's a mirrored partition):
    DISKPART> detail volume
      Disk ###  Status         Size     Free     Dyn  Gpt
      Disk 2    Online          298 GB  1024 KB   *
      Disk 1    Online          298 GB  1024 KB   *
    Read-only              : No
    Hidden                 : No
    No Default Drive Letter: No
    Shadow Copy            : No
    Offline                : No
    BitLocker Encrypted    : No
    Installable            : Yes
    Volume Capacity        :  297 GB
    Volume Free Space      :  268 GB
    Any suggestions?

  • Upgrading hyper-v 2008 r2 to 2012?

    is it possible/will it be possible to just upgrade hyper-v server from 2008 r2 to 2012 or will I have to reinstall the whole os and vms?

    "Hyper-V Server (Server Core) cannot be upgraded to Hyper-V Server 2012. You can choose to install
    a new copy of Hyper-V Server 2012 instead, but this is different from an upgrade, and does not keep your files, settings, and programs."
    Any know how to work around this problem?
    Yes - export your VM's and re-install your host OS!  It really doesn't add that much time.
    And here's a tip for quicker exports - if you have a VM that has several really large VHD's you can temporarily remove the VHD's from the guest VM config and then export.  I had an SBS 2011 VM with the Guest OS, Exchange, Swap and User data all on separate
    VHD's.
    I shut down the VM normally and then detached the large user data VHD's.  The export/import of the VM went much faster.  Once the Host OS was re-installed and the VM was re-imported, I just re-attched the user data VHD's before restarting the VM
    and the server in the VM was none the wiser.  I went through the trouble of keeping the VHDs in same location in the virtual SCSI controller in the guest VM configuration settings, but I don't know if that's strictly required or not.  It worked like
    a champ and didn't add that much time to the overall process of rebuilding the HyperV host OS.  If I ever get comfortable enough to switch to Server 2012 HyperV, I'll do the exact same process.  For something as simple as a hypervisor OS install,
    upgrading it doesn't make much sense to me!  As others have pointed out you are MUCH better off doing a clean install.  Especially if it won't upgrade it for you :o)

  • Windows 2012R2 Licensing w/ Hyper-V on Server 2008R2

    I know we're not "forced" to upgrade and by the time Server 2008R2 stops being supported we'll have well moved on storage-wise by then, i just wasn't sure if the virtual 2 hosts per licence was dependant on Server 2012 being the host OS... And I suppose, if you we were a VMWare shop, they could run 2 virtualised Server 2012R2s per licence too?

    squeak wrote:We currently use a MD3000i SAN for storage but Dell doesn't officially support it to run with Server 2012 and up.
    Time to get away from SAN!! This is a major issue. The SAN itself is a huge issue, of course, costly and risky and unnecessarily complex. But now that it is horrendously out of date and making you actually consider running an ancient version of HyperV this, right now, is the time to drop the SAN.
    Move to local disks and run current HyperV. Don't let the fact that you already own the SAN cloud your judgement. It is tempting to use it to attempt to justify the money spent sometime in the past. But that money is gone, let it go. Look at what makes the most sense for the business today based on what you have today. This is the "sunk cost fallacy" playing out.

  • How many licence for Windows Server 2012R2 in hyper-v cluster base on free Hyper-V Server 2012R2

    Hi
    I build cluster consist 4 nodes (2 procesors, 4 core per procesor=8 virtual processors per node). I installed free Hyper-V Server 2012 R2 on each node and created cluster.
    I've got one Windows Server 2012 R2 Standard. How many VMs (with Windows Server 2012 R2 Standrard as OS) can I run on this cluster using this DVD? 1, 2 or none?
    Thank you in advance
    Tomasz
    Kind Regards Tomasz

    The detail here is this:
    You are asking about the 'virtual instance granting' license.
    - this only applies if Windows Server is installed on the bare metal with the Hyper-V Role added. (regardless of the edition)
    - this only applies to licensing, it does not limit the number of VMs that you can run.
    - If there is a cluster, all nodes should be the same edition to remove any licensing ambiguity.
    This is strictly OS licensing for the VMs and has absolutely nothing to do with how many VMs you can run:
    Most likely your hardware will run out of physical resources before you reach the maximums outlined here:
    http://technet.microsoft.com/en-us/library/jj680093.aspx
    If you have a cluster - there can be a maximum of 8,000 running VMs
    If you have individual Hyper-V Servers there can be a maximum of 1,024 running VMs
    Do the math - you would need a minimum of ~8 cluster nodes to touch that 8,000 number.  But as you add nodes, you don't add HA VM capacity.  But you can run a combination of HA and non-HA VMs up to a the maximum of 1,024 running VMs per node. 
    In other words, mix and match if you want to push the boundary.
    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.

  • Migrate from server core 2008 r2 hyper-v with failover cluster volumes to server core 2012 r2 hyper-v with failover cluster volumes on new san hardware

    We are getting ready to migrate from server core 2008 r2 hyper-v with failover cluster volumes on an iscsi san to server core 2012 r2 hyper-v with failover cluster volumes on a new iscsi san.
    I've been searching for a "best practices" article for this but have been coming up short.  The information I have found either pertains to migrating from 2008 r2 to 2012 r2 with failover cluster volumes on the same hardware, or migrating
    to different hardware without failover cluster volumes.
    If there is anyone out there that has completed a similar migration, it would be great to hear any feedback you may have on your experiences.
    Currently, my approach is as follows:
    1. Configure new hyper-v with failover cluster volumes on new SAN with new 2012 r2 hostnodes and 2012 r2 management server
    2. Turn off the virtual machines on old 2008 r2 hyper-v hostnodes
    3. Stop the VMMS service on the 2008 r2 hostnodes
    4. copy the virtual machine files and folders over to the new failover cluster volumes
    5. Import vm's into server 2012 r2 hyper-v.
    Any feedback on the opertain I have in mind would be helpful.
    Thank you,
    Rob

    Hi Rob,
    Yes , I agree with that "file copy " can achieve migration.
    Also you can try "copy cluster wizard " :
    https://technet.microsoft.com/en-us/library/dn530779.aspx
    Best Regards,
    Elton Ji
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

  • Upgrading from SQL Server 2012 Standard to SQL Server 2014 Standard Failover Cluster

    Goal: To upgrade my default instance from SQL Server 2012 to SQL Server 2014 in a failover cluster.
    Given:
    1) Operating System Windows 2012 R2
    2) 2 Virtual Machines in a cluster with SQL Server as a Guest Cluster resource.  The two VMS are called APPS08 and APPS09.  They are our development environment that is setup similar to our production environment.
    Problem:  When running the SQL Server 2014 upgrade, I started on the VM that was not running the instance.  I then moved onto upgrading on the node that was running the instance.  As soon as the install attempt to failover the running instance
    an install error occurred that it could not failover.  After many install attempts I consistently received the error
    The SQL Server Failover cluster instance name 'Dev01'
    already exists as a cluster resource.  Opening Failover cluster manager there is no record of a DEV01.
    New Strategy:  Create a SQLCluster called DEV07.  At the end of the Install I get 'Resource for instance 'MSSQLSERVER' should not exists.  Neither I nor my Windows 2012 guy understand what Resource the install may be referring to.  
    We do not see anything out of the ordinary.
    Any suggestions as to what Resource may be seeing the default instance would be greatly appreciated.

    Hi PSCSQLDBA,
    As your description, you want to upgrade the default instance in SQL Server cluster.
    >> 'SQL Server failover cluster instance name 'Dev01' already exists as cluster resource'
    This error could occur when there is a previously used instance name which may not be removed completely.
    To work around the issue, please use one of the ways below.
    1. At command prompt, type Cluster res. This command will list you all the resources including orphan resources. To delete the orphan resource, type Cluster res <resource name>/delete.
    For more information about the process, please refer to the article:
    http://gemanjyothisqlserver.blogspot.in/2012/12/sql-2008r22012-cluster-installation.html
    2. Delete DNS entries, and force a replication of DNS to the other DNS servers.
    For more information about the process, please refer to the article:
    http://jon.netdork.net/2011/06/07/failed-cluster-install-and-name-already-exists/#solution
    >> 'Resource for instance 'MSSQLSERVER' should not exist'
    This error could occur when you already have MSSQLSERVER as a resource in the cluster, which may not be removed completely. To work around the issue, you could rebuild the SQL Server cluster node.
    Regards,
    Michelle Li

  • Services configuration for sql server 2008r2 in a Windows Cluster

    Hello,
    We have a Windows Server 2008 Cluster with Sql Server 2008r2 installed on node 2; when node 2 fails (we don't still know why, it's a 'bluescreen' long history), the service goes from node2 to node1, but sometimes the services are not automatically activated.
    What is the theoretical startup settings for sql services (for the sql and the agent), manual, disabled, automatic... ?
    Also, sometimes, the service for the sql server in node2 stops, but we don't know why, and we are not able to see any significant information on the event viewer. How can we trace why Sql Server stopped ?
    Thanks !

    >What is the theoretical startup settings for sql services
    Manual.  The cluster will start them.
    >How can we trace why Sql Server stopped ?
    Look in the SQL Server Log.
    David
    David http://blogs.msdn.com/b/dbrowne/

  • Can a SQL Server Failover Cluster Instance (FCI) be Implemented Between Two Hyper-V Hosted Virtual Machines?

    I haven't had the opportunity to implement a SQL Server Failover Cluster Instance (FCI) for over 10 years and that was done with two physical, identical database servers way back in the day of Windows Server 2003 and SQL Server 2000 (old school).
    Can a SQL Server 2008 R2 Failover Cluster Instance (FCI) be implemented between two Hyper-V hosted virtual machines? The environment in question already has Windows Server 2012 R2 Hyper-V hosts in place, so I'm just looking to see if this is even
    possible and/or supported when utilizing virtual machines.
    The client in question is currently using SQL Server 2008 R2 instances running on Win2008R2, Win2012, and Win2012R2, but I'd also be interested how this can be done or not with SQL Server 2012 or 2014 as well. Thanks in advance.
    Bill Thacker

    Yes, it can be done with Hyper-V guests. In fact, with Windows Server 2012 R2 Hyper-V, guests can use the Shared VHDX feature for shared storage used by Windows clusters. The guests can run Windows Server 2008 and higher provided that the Hyper-V Integration
    Services are installed to support Shared VHDX. The only challenge here is making the Hyper-V hosts highly available as well, running it on WSFC.
    Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
    Blog |
    Twitter | LinkedIn
    SQL Server High Availability and Disaster Recover Deep Dive Course

  • SQL Server 2008R2 Active-Active cluster with standard edition?

    Hi all,
    can I have a 2 node cluster (Windows Server 2008R2 Datacenter Edition: node_1 and node_2) forming a failover cluster with 2 instances of SQL Server 2008R2 Standard Edition (instance_A and instance_B) with:
    instance_A running on node_1
    instance_B running on node_2

    Following thread is on similar topic:
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/450dfb42-635b-4c99-ae9f-6b0a23e3430b/sql-server-2008-r2-standard-edition-failover-cluster?forum=sqldatabaseengine
    Kalman Toth Database & OLAP Architect
    SQL Server 2014 Design & Programming
    New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Maybe you are looking for