Backing up virtualised SQL Cluster on Hyper-V with DPM 2012 R2

I'm sure this must have been answered but I can't find it so far. I have a Server 2012 R2 Hyper-V cluster. On that cluster is a virtual SQL 2012 cluster. What is best practise for protecting the SQL cluster? Do I protect the VM through Hyper-V Host backups,
protect the Hyper-V guests directly, etc.?? Are there any good articles on this?
Thanks
Mark

Hi,
i would install a DPM Agent on all SQL Cluster Nodes an Backup the SQL Databases.
Additionally for Desaster Recovery, i would protect the VM, if your Disk space ist not enought for this, just Backup Systemstate of the CluserNodes
Seidl Michael | http://www.techguy.at |
twitter.com/techguyat | facebook.com/techguyat

Similar Messages

  • I want to deployment virtual machine by Hyper-V with windows 2012 server

    I want to deployment virtual machine by Hyper-V with windows 2012 server. So I need step by step guide line with screenshot and video link.
    Thanks,
    Qamrul

    Hi Qamrul,
    Additionally here is the link for hyper-v getting started guide (server2008 ) :
    http://technet.microsoft.com/en-us/library/cc732470(v=ws.10).aspx
    Best Regards
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • SQL cluster 2008 R2 migration to new Hardware in VM

    Hi,
    We have a task to migrate existing Physical SQL Cluster DB to new Hardware but in VM. (cannot argue with the client)
    hence our plan is to install new Cluster in VM with same Windows and SQL version i.e Win 2K8 R2 ENT w/SP and SQL 2K8
    R2 STD w/SP and use SQL mirroring option for the DB to migrate on the new Server (keeping the downtime to as low as possible and advantage of bringing the old server online in case of any issues..)
    Below points are for a single instance, couple of DB to migrate:
    Keep the  physical production server running
    In-Parallel build New SQL Cluster in VM (keep same version windows/sql)
    Keep Same drive letter for Quorum, MSDTC, DATA, LOG & Backup
    Keep the same Instance Name, SQL Network Name can be different (will be changed to old network name once the PROD is shutdown)
    Check all logins windows and SQL to be same on both the clusters
    Copy all the jobs, SSIS packages etc.. .create the location folder as per current server on the VM SQL Cluster
    Perform full backup of old cluster company-db databases or use the existing latest backup (full, differential, transaction)
    Restore databases in the new cluster with no recovery so additional log file or differential backup can be restored
    Create SQL Mirroring for the Database and select the principal server (old cluster) and the mirror server (new VM cluster)
    Choose mirroring without witness ( no auto failover as we don’t need the old server later)
    Start the mirroring – (hopefully everything synchronized and working)
    During the downtime –
    Stop the application/ client connection – if possible
    Failover the DB through Mirroring option
    Once the mirrored server becomes Principal and data is accessible – stop the mirroring
    Now the new VM SQL Cluster DB is online
    Shutdown the old cluster company-db (Node1 & Node2)
    Come back to VM SQL Cluster and change the Network name to the old server network name (so that client connections are not affected)
    Check if the DNS entries are updated with correct name and IP address
    Delete DNS entries for old company-db on DNS Servers if not deleted, delete the old server SQL network name in computer object
    Stop SQL Resources on the new VM SQL Cluster (take it offline all the resources)
    Bring online the SQL Resource and make sure the SQL resources are online and new network name is reachable
    Wait till you see machine name company-db in active directly (AD) and DNS server will have entry for company-db
    Verify connectivity for company-db from outside.
    If things are not going as per the plan then shut down the new VM cluster
    Revert back the DNS settings
    Power up the Old SQL Server
    The DB will show “restoring mode” – use command to make it online “RESTORE DATABASE (dbname) WITH RECOVERY”
     Check the DB
    Start using the OLD server again
    Troubleshoot the failed scenario ;)
    Need to know if the above steps are okay, and any consideration once the new VM SQL Cluster is online.
    Kindly let me know if there anything else to transfer apart from the logins, jobs, folder location etc.. !! 
    Many Thanks

    Hello,
    Well if you don’t change the instance name (name = ABC) then its OK.
    Try the following resources about transferring SQL Server logins:
    http://support.microsoft.com/kb/918992/en-us
    http://www.mssqltips.com/sqlservertip/2081/transfer-sql-server-jobs-task-and-transfer-sql-server-logins-task-in-ssis/
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • VM Protection running on Hyper-V 2012 R2 with DPM 2010

    Hi everyone,
    We recently setup  a new Hyper-V 2012 R2 server hosting virtual machine running with a Win2012 R2 server OS and 2008R2 standard Edition
    Our backup solution is still running DPM 2010.
    As I understand from the DPM Protection Support Matrix, You can only protect virtual machine running on a hyper-v server under Windows 2012 R2 OS with DPM 2012 R2. Isn't there possible any walkaround to have the vm protection working on dpm2010?
    Otherwise, if we choose to protect the VM at guest level instead of host-level, is DPM able to perform the recovery point?
    For instance, we've got a VM running a SQL database. We would like specifically to back up that SQL  database running on that virtual machine.Is DPM able to perfom that job?
    Regards,
    Evan

    Hi,
    To remain in a supported configuration you need to a DPM 2012 R2 server to protect the Windows 2012 R2 hyper-v server.  Unfortunately, the path to get there from DPM 2012 is not an easy one.
    Upgrade steps.
    Note: the Operating system and SQL requirements for DPM 2012
    System Requirements for DPM in System Center 2012
    http://technet.microsoft.com/en-us/library/hh757757.aspx
    1) On DPM 2010 install the latest update: KB2751231 Description of hotfix rollup package 7 for System Center Data Protection Manager 2010
    2) Update the Agents to 3.0.8195.0
    3) Backup the DPM 2010 database.
    4) Upgrade to DPM 2012 and update agents.
    5) Install the latest DPM 2012 update and Update agents.
    6) Backup the DPM 2012 database.
    7) Upgrade to DPM 2012 Sp1 and update agents.
    Note: The Operating system and SQL requirements for DPM 2012 Sp1
    System Requirements for DPM in System Center 2012 Sp1
    http://technet.microsoft.com/en-us/library/jj651645.aspx
    8) Install the latest DPM 2012 Sp1 update and update agents.
    KB2904723-Issues that are fixed in System Center 2012 Data Protection Manager SP1 Update Rollup 5
    http://support.microsoft.com/kb/2904723
    KB2904730-Description of System Center 2012 Service Pack 1 Update Rollup 5
    http://support.microsoft.com/kb/2904730
    9) Continue to DPM 2012 R2..
    Note: the Operating system and SQL requirements for DPM 2012 R2.
    System Requirements for DPM in System Center 2012 R2
    http://technet.microsoft.com/en-us/library/hh758176.aspx
    10) Backup the DPM 2012 Sp1 database.
    11) Upgrade to DPM 2012 R2 and update agents
    12) Install latest DPM 2012 R2 update and update agents.
    Else, you could stand up a new dedicated DPM 2012 R2 server from scratch to protect that new server and leave the DPM 2010 as is for current protection.  
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
    This posting is provided "AS IS" with no warranties, and confers no rights.

  • Can DPM 2012 R2 backup SQL Server 2012 AlwaysOn enabled databases

    Is it possible to use DPM 2012 R2 for backing up
    SQL Server 2012 AlwaysOn enabled databases ?
    Because if Alwayson configured for any Database , particular database is not available to select for backup.

    Hi,
    Yes, starting with DPM 2012 SP1 SQL AlwaysOn enabled databases can be protected as long as they are not part of sharepoint farm. DPM shows the Availability Groups under Cluster Group.
    You must explicitly add the system account NTAuthority\System or NT AUTHORITY\DPMRA to the Sysadmin group on SQL Server.
    Protecting SQL Server Data
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
    This posting is provided "AS IS" with no warranties, and confers no rights.

  • DPM 2012 R2 and Hyper-V Replication, huge conflict and failure to backup

    I have recently created new 2012 R2 servers with DPM 2012 R2 in attempts to upgrade an environment.
    When attempting to create Protection Groups for Hyper-V VM, DPM will consistently omit any VM that happens to have Hyper-V Replication enabled, whether that server is the primary VM instance or a replica VM instance.  ALL other Hyper-V VMs are listed,
    only those with Replication enabled are omitted.  This happens on both DPM 2012 R2 servers, exactly the same results - all VMs without Hyper-V Replication enabled are listed, none of the VMs with replication enabled are visible in the list.
    Obviously we need to be able to backup VMs with Hyper-V replication since replication is only a tiny portion of a DR strategy, it doesn't cover ANY recovery scenario other than the loss of the primary VM - it doesn't allow for restoring any missing or damaged
    files or undoing any other changes to the VM.
    The DPM 2012 R2 server have the latest update rollup (#4) applied and the protection agents have also been updated.
    Looking for some hints since DPM 2012 R2 is supposed to support backing up both the primary and replica VMs, especially when the Hyper-V host if Server 2012 R2.
    Might have to use Windows Server Backup or Veeam's free Hyper-V backup since aside from enabling Hyper-V replication to keep a couple snapshots, DPM isn't a viable backup options in combination with Hyper-V replication.

    As per the following blog:
    http://blogs.technet.com/b/dpm/archive/2014/04/25/backing-up-of-replica-vms-using-dpm.aspx
    you should be able to backup Hyper-V VMs even if they are replica VM.
    When you configure DPM to protect both primary and recovery hosts, VM will appear on any of the Servers as it will have the same GUID.
    So, protect primarya nd recovery hosts using different DPM or if you want to protect both primary and recovery using same DPM, make sure that you check both servers so as to discover VM.
    Regards, Trinadh [MSFT] This posting is provided AS IS with no warranties, and confers no rights. If you found the reply helpful, please MARK IT AS ANSWER. Looking for source of information for DPM? http://blogs.technet.com/b/dpm/ http://technet.microsoft.com/en-in/library/hh758173.aspx

  • Moving Physical SQL Cluster into Virtual SQL Cluster based on Hyper-V Failover

    Hello All............I have a SQL Cluster based on Physical Hardware that has Three-3 instances as well. I have setup a Hyper-V Failover Cluster (2012 R2) and have built Virtual/Guest SQL Cluster (2012 R2) upon it.  Now, I intend to move
    the instances/databases from Physical SQL Cluster to Virtual SQL Cluster.
    1.  Is this supported?  If so, I would appreciate any guidance on it?
    2.  Is P2V of SQL Cluster supported in Hyper-V Failover Cluster based on Windows Server 2012 R2?

    Hi Sir,
    Please refer to the following blog regarding moving SCCVM SQL database to another SQL server:
    http://blogs.technet.com/b/configurationmgr/archive/2013/04/02/how-to-move-the-configmgr-2012-site-database-to-a-new-sql-server.aspx
    It is quoted from the  similar thread :
    https://social.technet.microsoft.com/Forums/en-US/a1558842-cdf5-4e5f-8f10-d660e96eae1b/migration-sql-for-sccm-2012?forum=configmanagermigration
    But it seems that is a migration of system center production , I would suggest you to post the question to system center forum ：
    https://social.technet.microsoft.com/Forums/en-US/home?forum=configmanagermigration%2Coperationsmanagergeneral&filter=alltypes&sort=lastpostdesc
    Best Regards,
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • SQL Cluster - Unable to obtain IP Address from System Center IP Pool

    Hi everyone,
    we are trying to deploy a SQL cluster into a windows azure pack tenant cloud.
    Our azure pack environment contains:
    - 4X Hyper-V server in a failover cluster
    - 1X SCVMM server
    - multiple WAP server
    Steps we have done:
    -    Windows failover cluster is installed and configured successfully
    -    Quorum disk was configured successfully
    -    SQL server 2014 installation (via static IP) is successfully. But routing between the VMs is not possible.
    -    SQL server 2014 installation (via DHCP) fails at the end of the installation with following error:
            -> We used DHCP to obtain an IP from the scvmm IP pool.
    (01) 2015-04-22 15:29:11 Slp: Running Action: cluster_ip_address_cluster_config_Cpu64
    (01) 2015-04-22 15:29:11 Slp: Action Data:
    (01) 2015-04-22 15:29:11 Slp:   Feature = SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64
    (01) 2015-04-22 15:29:11 Slp:   Scenario = install
    (01) 2015-04-22 15:29:11 Slp:   Timing = ConfigNonRC
    (01) 2015-04-22 15:29:11 Slp:   ConfigObjectType = Microsoft.SqlServer.Configuration.ClusterConfiguration.ClusterIPAddressPrivateConfigObject
    (01) 2015-04-22 15:29:11 Slp:   FeatureName = SQL_Engine_Core_Inst
    (01) 2015-04-22 15:29:11 Slp:   FeatureCpuType = Cpu64
    (01) 2015-04-22 15:29:11 Slp:   FeaturePackageId = sql_engine_core_inst
    (01) 2015-04-22 15:29:11 Slp:   FeatureClusterState = CompleteFailoverCluster
    (01) 2015-04-22 15:29:11 Slp: Creating IPv4 address 'SQL IP Address 1 (SQLADFS)'.
    (01) 2015-04-22 15:29:11 Slp: Creating cluster resource 'SQL IP Address 1 (SQLADFS)' of type 'IP Address' in group 'SQL Server (ADFS)'
    (01) 2015-04-22 15:29:11 Slp: Bringing IP address resource 'Type='IP Address' NetworkName='Cluster Network 1' Group='SQL Server (ADFS)' Resource='SQL IP Address 1 (SQLADFS)'' online
    (01) 2015-04-22 15:29:11 Slp: Bringing cluster resource 'SQL IP Address 1 (SQLADFS)' online
    (01) 2015-04-22 15:29:12 Slp: Prompting user if they want to retry this action due to the following failure:
    (01) 2015-04-22 15:29:12 Slp: ----------------------------------------
    (01) 2015-04-22 15:29:12 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    (01) 2015-04-22 15:29:12 Slp: Inner exceptions are being indented
    (01) 2015-04-22 15:29:12 Slp:
    (01) 2015-04-22 15:29:12 Slp: Exception type: Microsoft.SqlServer.Configuration.Cluster.ResourceOnlineException
    (01) 2015-04-22 15:29:12 Slp:     Message:
    (01) 2015-04-22 15:29:12 Slp:         The cluster resource 'SQL IP Address 1 (SQLADFS)' could not be brought online.  Error: There was a failure to call cluster code from a provider. Exception message: Generic failure
    . Status code: 5023. Description: The group or resource is not in the correct state to perform the requested operation.
    (01) 2015-04-22 15:29:12 Slp:         .
    (01) 2015-04-22 15:29:12 Slp:     HResult : 0x86d8003a
    (01) 2015-04-22 15:29:12 Slp:         FacilityCode : 1752 (6d8)
    (01) 2015-04-22 15:29:12 Slp:         ErrorCode : 58 (003a)
    (01) 2015-04-22 15:29:12 Slp:     Data:
    (01) 2015-04-22 15:29:12 Slp:       resourceName = SQL IP Address 1 (SQLADFS)
    (01) 2015-04-22 15:29:12 Slp:       errorMessage = There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The group or resource is not in the correct state
    to perform the requested operation.
    (01) 2015-04-22 15:29:12 Slp:       WatsonData = Microsoft.SqlServer.Configuration.Cluster.ResourceOnlineException@58
    (01) 2015-04-22 15:29:12 Slp:       DisableRetry = true
    (01) 2015-04-22 15:29:12 Slp:     Inner exception type: Microsoft.SqlServer.Configuration.Cluster.ClusterProviderDetailedException
    (01) 2015-04-22 15:29:12 Slp:         Message:
    (01) 2015-04-22 15:29:12 Slp:                 There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The
    group or resource is not in the correct state to perform the requested operation.
    (01) 2015-04-22 15:29:12 Slp:                 .
    (01) 2015-04-22 15:29:12 Slp:         HResult : 0x86d70002
    (01) 2015-04-22 15:29:12 Slp:                 FacilityCode : 1751 (6d7)
    (01) 2015-04-22 15:29:12 Slp:                 ErrorCode : 2 (0002)
    (01) 2015-04-22 15:29:12 Slp:         Data:
    (01) 2015-04-22 15:29:12 Slp:           ExceptionMessage = Generic failure
    (01) 2015-04-22 15:29:12 Slp:           StatusCode = 5023
    (01) 2015-04-22 15:29:12 Slp:           Description = The group or resource is not in the correct state to perform the requested operation.
    (01) 2015-04-22 15:29:12 Slp:           WatsonData = Microsoft.SqlServer.Configuration.Cluster.ClusterProviderDetailedException@2
    (01) 2015-04-22 15:29:12 Slp:         Stack:
    (01) 2015-04-22 15:29:12 Slp:                 at Microsoft.SqlServer.Configuration.Cluster.WmiClusterResource.Online(Int32 timeout)
    (01) 2015-04-22 15:29:12 Slp:                 at Microsoft.SqlServer.Configuration.Cluster.ClusterResource.Online(Int32 timeout)
    (01) 2015-04-22 15:29:12 Slp:         Inner exception type: System.Management.ManagementException
    (01) 2015-04-22 15:29:12 Slp:             Message:
    (01) 2015-04-22 15:29:12 Slp:                         Generic failure
    (01) 2015-04-22 15:29:12 Slp:             HResult : 0x80131501
    (01) 2015-04-22 15:29:12 Slp:             Data:
    (01) 2015-04-22 15:29:12 Slp:               WmiErrorCode = Failed
    (01) 2015-04-22 15:29:12 Slp:               WatsonData = Failed@5023
    (01) 2015-04-22 15:29:12 Slp:               Description = The group or resource is not in the correct state to perform the requested operation.
    (01) 2015-04-22 15:29:12 Slp:               ErrorType = 1
    (01) 2015-04-22 15:29:12 Slp:               Operation = ExecMethod
    (01) 2015-04-22 15:29:12 Slp:               ParameterInfo = MSCluster_Resource.Name="SQL IP Address 1 (SQLADFS)"
    (01) 2015-04-22 15:29:12 Slp:               ProviderName = WinMgmt
    (01) 2015-04-22 15:29:12 Slp:               StatusCode = 5023
    (01) 2015-04-22 15:29:12 Slp:             Stack:
    (01) 2015-04-22 15:29:12 Slp:                         at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
    (01) 2015-04-22 15:29:12 Slp:                         at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject
    inParameters, InvokeMethodOptions options)
    (01) 2015-04-22 15:29:12 Slp:                         at Microsoft.SqlServer.Configuration.WMIInterop.Resource.BringOnline(UInt32 TimeOut)
    (01) 2015-04-22 15:29:12 Slp:                         at Microsoft.SqlServer.Configuration.Cluster.WmiClusterResource.Online(Int32 timeout)
    (01) 2015-04-22 15:29:12 Slp: ----------------------------------------
    We have tried to reinstall the servers multiple times, without result.
    Can anyone assist us in this case?
    Thanks
    Kind Regards
    Julian

    Hi Darryl,
    thanks for your supply.
    We don't have an DHCP in the Cloud. System Center DHCP is used for assigning IP addresses and routing inforamtion to the vms.
    This works fine for assigning IP addresses to the vms.
    At my current point of understanding network virtualisation with system Center, we do not have an alternative to this way of assigning IP addresses.
    Kind Regards
    Julian

  • DPM 2012 R2 CU4 protecting SQL 2014 AlwaysOn AG with Failover Cluster vs. DR location

    Hello!
    We have a problem protecting any Database of SQL 2014 AlwaysOn Availability Group with SQL Failover Cluster Instance when moved to DR location. Everything is protected using DPM 2012 R2 CU4 from Primary location.
    FACTS
    - all servers are Windows Server 2012 R2
    - all servers are Virtual (except Hyper-V hosts obviously:)
    - that means virtualization is based on Windows Server 2012 R2 Hyper-V
    - all clusters (SQL, Exchange,...) are Guest Clusters on Hyper-V
    - SQL 2014
    - DPM 2012 R2 CU4
    - Primary and DR location 
    SETUP
    SQL
    - Primary location: SQL 2014 Guest Cluster with SQL Failover Cluster Instance using Shared VHDX disks
    - DR location: SQL 2014 Standalone using VHDX disks
    - AlwaysOn Availability Group expands between the primary and DR location.
    DPM
    - Primary location: DPM 2012 R2 CU4
    - DPM 2012 R2 CU4 Agents installed on every possible SQL 2014 Server.
    SCENARIO
    - DPM is backing up all the SQL Databases normally as long as they exist on any SQL Cluster Node on Primary location.
    - As soon as any Database is moved to DR location, that Database is not backed up anymore with the following error.
    DPM ERROR
    Starting synchronization on SqlServerName\DatabaseName failed:
    Error 104: An unexpected error occurred while the job was running.
    Error details: The system cannot find the path specified (0x80070003)
    Recommended action: Retry the operation.
    TROUBLESHOOTING
    - Tried to modify SQL Protection Group in DPM Server while Database was active on DR location
    > error enumerating volumes or drives D:\, E:\, F:\ (I don't have exact error atm)
    > this looks like DPM is not aware that DPM is active on DR location to me
    - Checked Technet, blogs and forums; no useful information
    QUESTION
    Is this expected or by-design behavior? Is this a bug? I am aware there were quite some issues backing up AG's from DPM 2012 SP1 ans SQL 2012 on.
    Does anybody have a lab of that kind to try it out?
    Thank you!
    Best Regards,
    Damjan Grimšič
    Lpd

    OK. The issue has been resolved. Issue was related to possible Disks Owners in Failover Cluster Manager Console for SQL Cluster.
    In Primary's site SQL Cluster Failover Manager Console / Storage / Disks.
    SQL Server(s) from Secondary location need(s) to be unchecked as Possible owner(s) in Advanced Policies for all relevant Volumes.
    Lpd

  • DPM 2012 R2 Hyper-V backup of SQL server VM

    Hello!
    I have a question about using DPM 2012 R2 in Hyper-V 2012 R2 cluster and backing up Windows 2003 VM, that has SQL 2008 installed.
    When i use VM, host level backup with DPM2012 R2, would it trigger a full DB backup on SQL server or not?
    Problem is, that we are using SQL (maintanance plans) for backing up databases and doing transaction logs backup. 
    I want to back up the whole VM, but i want to be sure, that this would not mess up SQL backup inside the VM?
    Is it possible, that i wont install DPM agent inside the SQL server VM? But can i then still restore files from the VHD/X or only entire VM?

    Hi,
    Apply the following registry entry in the GUEST virtual machine so application logs are not truncated by host level backups.
    Location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Virtualization\VssRequestor
    Name: BackupType
    Type: REG_DWORD
    Value: 1
    If this registry entry is created and its value is set to 1 , application backup will not be affected by the virtual machine backup operation on the server that is running Hyper-V. If this registry entry does not exist, or if its value is 0 , then host level
    backups will truncate logs in the guest.
    Yes - you can perform item level recovery for files inside the .vhd by double-clicking the .vhd while browsing to restore the VM.  That will mound the .vhd and allow you to copy files out without having to restore the entire .vhd file.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
    This posting is provided "AS IS" with no warranties, and confers no rights.

  • Question on sql cluster failover behaviour

    Hi Experts,
    I have a doubt on SQL Cluster.
    In SQL cluster, If we MOVE the group or failover the group to another node what happens to the user connections(say 100 conn's) and ongoing open transactions during failover?
    Will all connections gets disconnected and open transactions gets rollbacked or the connections and txns will be moved to other node?
    Could anyone shed some insight on this?
    Thank you.

    All connections get disconnected an ongoing transactions have to be rolled back. Its like restarting the service, just on the other node.
    Bodo Michael Danitz - MCT, MCITP - free consultant - performance specialist - www.sql-server.de

  • Does DPM 2012 R2 still needs DataSourceGroups.xml and MaxAllowedParallelBackups key when using Hyper-V VSS Software Writer to backup Server 2012 R2 Cluster

    Hi,
    Does DPM 2012 R2 still needs DataSourceGroups.xml and MaxAllowedParallelBackups key when using Hyper-V VSS Software Writer to backup Server 2012 R2 Hyper-V Cluster with CSV's? Can't find a clear answer somewhere.
    Thanx for helping me out.
    DJITS.

    Configure CSV backups
    If you are running Hyper-V on Windows Server 2008 R2 and you’re backing up multiple clusters with DPM, you need to ensure that only one backup uses the same CSV at any one time. To do this, follow the instructions in
    Serialize virtual machine backups.
    If you’re using software VSS with Hyper-V on Windows Server 2008 R2, do the following
    Serialize virtual machine backups per node            
    Serialize virtual machine backups per CSV LUN            
    Have a nice day !!!

  • How to migrate SQL Cluster into Virtual SQL server or Virtual SQL Cluster

    Hello All,
    Currently we will be attempting to migrate a SQL cluster of (2 systems) into are virtual enviroment.  We have been tracking the system requirements with Vmware Consolidation Tool and IO Meter to make sure our hosts have enough resources to accomidate this.  All the metrics coming back looks like it will run just fine virtulized as the cluster was just for failover purposes anyhow and not for performance purproses.  With that said a few questions have come up.
    1.)  What is the best way to virtulize this or to convert it (P2V)
         -  Should we just create a new Virtual Machine and install the same version of SQL and do a manual migration to the new SQL server and leave it as 1 SQL server with HA
         -  Or is there a way to P2V this kind of a setup ? if so what are the steps involved?
    2.)  If a P2V is possible I was under the impression that you will have to use a RAW mapping for the hard disks otherwise the cluster will not work ?  Can anyone speak to this? as I'm pretty sure I have clustered windows server 2008 without RAW mapping before but not with SQL

    Another quick question.  The Vmware SQL Clustering KB article says:
    vSphere MSCS Setup Limitations
    Before you set up MSCS, review the list of functionality that is not supported for this release, and any
    requirements and recommendations that apply to your configuration.
    The following environments and functionality are not supported for MSCS setups with this release of vSphere:
    n Clustering on iSCSI, FCoE, and NFS disks.
    n Mixed environments, such as configurations where one cluster node is running a different version of ESX/
    ESXi than another cluster node.
    n Use of MSCS in conjunction with VMware Fault Tolerance.
    n Migration with VMotion of clustered virtual machines.
    n N-Port ID Virtualization (NPIV)
    n With native multipathing (NMP), clustering is not supported when the path policy is set to round robin.
    n You must use hardware version 7 with ESX/ESXi 4.0.
    Can you not do clustering if your shared storage is iSCSI ? or can you not do RAW mapping with it to create the cluster ?

  • Shared SQL Cluster or dedicated

    Can we use shared SQL cluster instance for Lync 2013 deployment or Lync must have dedicated SQL servers either for mirroring purpose or cluster
    User load 2200, with EV
    Absar

    Hi,
    1. SQL clustering topologies are not supported for new Lync Server 2013 deployments. For Back End Server high availability, SQL mirroring is the recommended and supported option.
    2. You can collocate each of the following databases on the same database server:
    Back-end database
    Monitoring database
    Archiving database
    Persistent Chat database
    Persistent Chat compliance database
    You can collocate any or any or all of these databases in a single instance of SQL Server or use a separate instance of SQL Server for each, with the following limitations:
    Each instance of SQL Server can contain only a single back-end database, a single Monitoring database, a single Archiving database, a single Persistent Chat database, and a single Persistent Chat compliance database.
    The database server cannot support more than one Front End pool, one Archiving deployment, and one Monitoring deployment, but it can support one of each, regardless of whether the databases use the same instance of SQL Server or separate instances of SQL
    Server.
    More details:
    https://technet.microsoft.com/en-us/library/gg398102.aspx
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • 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] .

Maybe you are looking for