Upgrade and Migration Speaker.

Upgrade and Migration Speaker

Agenda Skype for Business Upgrade and Migration
11/19/2018 5:01 AM Skype for Business Upgrade and Migration Overview, In-place upgrade, Side by Side, Tri-existence, consolidation Skype for Business In-place Upgrade Step by Step SQL AlwaysOn Availability Groups Upgrading from SQL Mirroring, Step by Step Known Issues Slide Objective: Introduce the overall session agenda. Notes: During this session we will review the steps required in order to migrate from Lync Server 2010/2013 to Skype for Business Server We will focus on the specific technical steps required as well as review some detailed migration experiences at the end of the session. As we progress through each step we will review the various considerations you might think about for your specific migration. © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Terms Upgrade Migration Co-existence Interoperability
Skype for Business 11/19/2018 5:01 AM Terms Upgrade Installing a newer version of software on a server or a client computer Migration Moving your production deployment from a previous version of Lync Server 2010/2013 to Skype for Business Server 2015 Co-existence The temporary environment that exists during migration when some functionality has been migrated to Skype for Business Server 2015 and other functionality still remains on a prior version (Lync Server 2010/2013) Interoperability The ability of your deployment to operate successfully during the period of coexistence © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Skype for Business Server Upgrade and Migration Overview

Upgrade or Migrate? Skype for Business Server 2015 Lync Server 2013
Supports the same hardware as Lync Server 2013 Supports side by side upgrade Introduces in-place upgrade Lync Server 2013 In-place Upgrade is the preferred method to upgrade for Lync Server 2013 to Skype for Business Requires Lync Server CU5 or newer Use side by side upgrade if hardware needs to be replaced Lync Server 2010 No in-place upgrade support Requires side by side Migration Tri-existence Not supported Consolidate to one supported version (2010 / 2013) first

In-place upgrade – overview
What is it? Upgrade from Lync Server 2013 to Skype for Business Server 2015 using existing hardware Benefits Preserve existing hardware/server investments Smoother upgrade process without extensive planning Reduce the overall cost for deployment Two modes of in-place upgrade Online mode – User are moved during the upgrade, no service downtime Offline mode – Service downtime during the upgrade process

“Online” Mode In-Place Upgrade Steps
Pool 1 empty Move all Pool 1 users 1 Pool 1 Lync Server 2013 CU5+ Pool 2 Lync Server 2013 CU5+ In-place Upgrade to Skype for Business Pool 2 empty 2 Move all Pool 1 users 4 Test and Verify functionality 3 Move all Pool 2 users 5 Pool 1 Skype for Business 2015 Pool 2 Lync Server 2013 CU5+ In-place Upgrade to Skype for Business 6 Move back Pool 2 users 8 Test and Verify functionality 7 Pool 1 Skype for Business 2015 Pool 2 Skype for Business 2015

“Offline” Mode In-Place Upgrade Steps
Inform users “Service unavailable” Inform users “Service unavailable” 1 5 Pool 1 Down time Pool 1 Lync Server 2013 CU5+ Pool 2 Lync Server 2013 CU5+ In-place Upgrade to Skype for Business In-place Upgrade to Skype for Business 2 6 Test and Verify functionality Pool 2 Down time Test and Verify functionality 3 7 Pool 1 Skype for Business 2015 Pool 2 Lync Server 2013 CU5+ Inform users “Service Available” Inform users “Service Available” 4 8 Pool 1 Skype for Business 2015 Pool 2 Skype for Business 2015

“Side-by-Side” Migration Overview
Similar to migration from Lync Server 2010 to Lync Server 2013 Build a new pool in parallel Move the users Deprecate the old pool Need to consider impact to OAuth configuration when completing the migration When removing servers, make sure connection points are moved first Reconfigure Exchange 2013 partner application Configure-EnterprisePartnerApplication.ps1 to point to the new Skype for Business Server 2015 authentication metadata URL

“Side-by-Side” Migration Upgrade Steps
Introduce a new Skype for Business pool 1 Pool 1 Lync Server 2010 / 2013 Pool 2 Skype for Business 2015 Move all Pool 1 users to the new pool 2 Pool 2 Skype for Business 2015 Pool 1 Lync Server 2010 / 2013 Deprecate the empty Lync Pool 3 Pool 2 Skype for Business 2015 Pool 1 Lync Server 2010 / 2013

Tri-existence When the environment consists of Lync Server 2010 and Lync Server 2013, consolidation to a single supported version is “mandatory” before Skype for Business Server 2015 can be introduced The preferred path is to consolidate to Lync Server 2013 to be able to take advantage of an “in-place” upgrade

“Consolidation Upgrade” Steps
Move all Pool 1 users to the a new Lync 2013 pool Add a new Lync 2013 Pool to the organization 2 1 Pool 1 Lync Server 2010 Pool 2 Lync Server 2013 Pool 3 Lync Server 2013 Single version Deprecate the Lync pool 3 Pool 1 Lync Server 2010 Pool 2 Lync Server 2013 Pool 3 Lync Server 2013 Upgrade to Skype for Business In-place or side by side 4 Pool 4 Skype for Business 2015 Pool 5 Skype for Business 2015

“In-place” Upgrade Order and Recommendations
No in-place upgrade using pool failover Don’t start services in mixed mode Don’t un-pair the pools before upgrade Ensure minimal time when the pools are paired with different versions Upgrade order Inside  Outside User pools first Shared components later (mediation server, Director, edge, CMS pool, etc.)

Roles Supported for “In-Place” Upgrade
Pools/Roles Upgrade to Skype for Business Server 2015 How to upgrade? Front End pool Yes Topology Builder + in-place upgrade setup Director pool Mediation pool Persistent Chat pool Edge pool Trusted Application pool Survivable Branch Server (SBS) No No support for in-place upgrade of SBS Survivable Branch Appliance (SBA) No support for in-place upgrade of SBAs SQL Server store Yes. From Mirroring to Availability Group SQL reconfiguration + Topology Builder File store n/a PSTN gateway Trunk Office Web Apps Server

SQL Support for Skype for Business Server 2015
SQL “In-place“ upgrade Seamlessly upgrades SQL Express 2012 to SQL Express 2014 Also upgrades all the local copies of the database Lync/Skype for Business Version Clustering SQL Version(s) Supported Mirroring AlwaysOn Availability Groups Lync Server 2010 Yes 2008 R2 SP2 (SE/EE) N/A Not supported Lync Server 2013 2012 SP1 (SE/EE) Skype for Business Server 2015 2014 (SE/EE) 2012 SP1 (EE) 2014 (EE) Note SQL Server Standard Edition is sufficient for SQL Server Failover Clustering with two nodes and SQL Server Mirroring SQL Server Enterprise Edition is required for SQL Server Failover Clustering with 3 or more nodes in the same cluster and for SQL Server AlwaysOn availability scenarios

Skype for Business Server In-place upgrade – Step by Step

“In-Place” Upgrade Steps
Install prerequisites Upgrade, publish topology, and upgrade databases using Topology Builder Stop the services on all the servers in the pool to be upgraded Run Setup.exe to upgrade the server Start services on all the servers in the upgraded pool STEP 2 STEP 3 STEP 4 STEP 5

Also for the Local SQL Express instance!
Skype for Business 11/19/2018 5:01 AM In-Place Upgrade STEP 1 Install prerequisites Install CU5+ latest hotfix to Lync 2013 topology PowerShell RTM version ( ) or later Have at least SQL Server 2012 SP1 installed Windows Server 2008 R2 - KB Windows Server KB Windows Server 2012 R2 - KB Also for the Local SQL Express instance! © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Skype for Business 11/19/2018 5:01 AM In-Place Upgrade STEP 2 Upgrade, publish topology, and upgrade databases using Topology Builder Lync Topology builder cannot be used Target should not have any Lync components Target can be a 64bit Windows Client OcsCore or any other Lync components should not be installed Launch Setup.exe from Skype for Business Server build Install administrative tools © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Skype for Business 11/19/2018 5:01 AM In-Place Upgrade STEP 2 Upgrade, publish topology, and upgrade databases using Topology Builder To confirm update of databases you can run Install-CsDatabases from Topology Builder If your services are collocated with your databases (Service and Store on the same machine) running Setup.exe/ OcsBootstrapper will automatically upgrade your local databases for you. (Upgrade, Publish topology and upgrade databases in less than 10 minutes!) Note Topology Builder will automatically upgrade the databases © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Skype for Business 11/19/2018 5:01 AM In-Place Upgrade STEP 3 Stop the services on all the servers in the pool to be upgraded Stop the Lync services on every Front End server in the pool All services on all Front End servers must be stopped, verify before starting the upgrade Stop-CsWindowsService -ComputerName FE01.tailspin.local Stop-CsWindowsService -ComputerName FE02.tailspin.local Stop-CsWindowsService -ComputerName FE03.tailspin.local Get-CsWindowsService Status Name ActivityLevel Stopped RTCATS Current Active Calls=0 Stopped RTCIMMCU Active Conferences=0,Connected Users=0 Stopped RTCDATAMCU Active Conferences=0 Stopped RTCAVMCU Number of Conferences=0,Number of Users=0 Stopped RTCASMCU Active Conferences=0,Connected Users=0 Stopped RTCMEDSRV Current Outbound Calls=0,Current Inbound Calls=0,Cu... © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

In-Place Upgrade Run Setup.exe to upgrade the server STEP 4
Skype for Business 11/19/2018 5:01 AM In-Place Upgrade STEP 4 Run Setup.exe to upgrade the server Setup should be run using elevated/administrator command prompt Switch Description /? Display help information /SourceDirectory:<Path> Set source directory of MSI /BootstrapCore Install admin console /BootstrapLocalMgmt Install local management store /Bootstrap Install all roles /BootstrapSqlExpress Prepare SQL Express RTC instance /Scorch Remove roles installed on machine /InplaceUpgrade Force Skype for Business Server Setup to perform an upgrade /SilentUpgrade Supress all UI and perform an upgrade /DownloadUpdates Indicates whether Skype for Business Server should discover and include product updates from Microsoft Update. Can be used only with the following parameters: BootstrapCore, BootstrapLocalMgmt, BootstrapSqlExpress, or InplaceUpgrade + SilentUpgrade © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

In-Place Upgrade Run Setup.exe to upgrade the server Smart Setup
Skype for Business 11/19/2018 5:01 AM In-Place Upgrade STEP 4 Run Setup.exe to upgrade the server Smart Setup Download the latest updates from the internet Requires internet connectivity No need for updates after installation © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

In-Place Upgrade Run Setup.exe to upgrade the server Installation
Skype for Business 11/19/2018 5:01 AM In-Place Upgrade STEP 4 Run Setup.exe to upgrade the server Installation Verifies requirements Uninstalls unused server roles Upgrades databases Installs new server roles Verifies the installation © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Introduced in Skype for Business
11/19/2018 5:01 AM In-Place Upgrade STEP 1 STEP 2 STEP 3 STEP 4 STEP 5 Install prerequisites Upgrade, publish topology, and upgrade databases using Topology Builder Stop the services on all the servers in the pool to be upgraded Run Setup.exe which will launch in-place upgrade UI Start services on all the servers in the upgraded pool at the same time (use the Start-CSPool cmdlet) Introduced in Skype for Business Starts all Front Ends © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

AlwaysOn Availability Groups Upgrading from SQL Mirroring – Step by Step

SQL in-place upgrade support
AlwaysOn minimum server requirements SQL Server 2012 SP1 Enterprise Edition SQL Server 2014 Enterprise Edition Supported only for Skype for Business Server pools Previous versions do not support SQL 2014 In-place upgrade from SQL 2012 SP1 standalone to SQL 2014 Availability Groups In-place upgrade from SQL 2012 SP1 mirroring to SQL 2014 Availability Groups All other in-place upgrade scenarios for SQL Servers are currently unsupported Full database backup prior to in-place upgrade is recommended Change compatibility level for each database after upgrade Select SQL Server 2014 (120) Set using Transact-SQL (optional) ALTER DATABASE cpsdyn SET COMPATIBILITY_LEVEL = 120; GO

Upgrading from SQL Mirroring
Skype for Business 11/19/2018 5:01 AM Upgrading from SQL Mirroring STEP 1 Failover all databases to the Primary SQL server STEP 2 Uninstall each database type and drop databases on Mirror server STEP 3 Disable database mirroring and publish the topology STEP 4 Enable AlwaysOn Availability Groups STEP 5 Create AlwaysOn Availability Group for the existing backend databases STEP 6 Add new SQL Store using the FQDN of the Availability Group Listener STEP 7 Associate the pool with the new SQL Store and publish the topology © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Skype for Business 11/19/2018 5:01 AM Upgrading from SQL Mirroring STEP 1 Failover all databases to the Primary SQL server (if needed) Verify databases are not failed over Use Get-CsDatabaseMirrorState to find the Principal server for each database All databases should be on the Primary server Use Invoke-CsDatabaseFailover –NewPrincipal Primary to failback databases DatabaseName StateOnPrimary Rtcab Principal Rtcxds Principal Rtcshared Principal Rgsconfig Principal Rgsdyn Principal Cpsdyn Principal StateOnPrimary should read Principal © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Skype for Business 11/19/2018 5:01 AM Upgrading from SQL Mirroring STEP 2 Uninstall each database type and drop databases on Mirror server Deprecate the Mirror databases Run Uninstall-CsMirrorDatabase –DropExistingDatabasesOnMirror for each database type Run Get-CsDatabaseMirrorState and verify that the StateOnMirror value is DatabaseUnavailable for all previously mirrored databases Note: verify Mirror server using SQL Server Management Studio, manually delete any databases that could not be dropped by the Uninstall-CsMirrorDatabase cmdlet DatabaseName : rtcab StateOnPrimary : DatabaseInaccessibleOrMirroringNotEnabled StateOnMirror : DatabaseInaccessibleOrMirroringNotEnabled MirroringStatusOnPrimary : MirroringStatusOnMirror : © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Skype for Business 11/19/2018 5:01 AM Upgrading from SQL Mirroring STEP 3 Disable database mirroring and publish the topology In Topology Builder, open the properties of the pool Deselect the Enable SQL Server store mirroring option Publish the topology © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Skype for Business 11/19/2018 5:01 AM Upgrading from SQL Mirroring STEP 4 Enable AlwaysOn Availability Groups Add the Windows Server Fail Over Clustering (WSFC) feature to each SQL node Validate the cluster configuration Create a new Windows Server Fail Over Cluster Configure Cluster Quorum Settings Enable AlwaysOn Groups © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Installing the Windows Server Failover Clustering Feature
Windows Failover Clustering Built in Windows Server Feature Installed through “Add Roles and Feature Windows Server 2008 R2 SP1 or Higher Important Cluster nodes cannot be Active Directory domain controllers Cluster nodes must be from the same Active Directory domain Cluster nodes must be connected to the same network subnet

Validating the Cluster Configuration
Adding cluster nodes Add the servers that will be part of the cluster All new nodes will be verified and tested

Node validation All new nodes will be verified and tested Address and fix all errors and warnings

Successful validation Select “Create the Cluster now using the validated nodes” A new Windows Failover cluster will be ceated using all configured nodes

Creating the Cluster Creating the cluster
Define an administrative cluster name For cluster administration only Not used by Skype for Business Automated DNS registration for IP Address

Uncheck “Add all eligible storage to the cluster” “Always On” does not require / utilize shared storage

A cluster consisting of the the configured nodes is created

Configuring Quorum Settings
Microsoft Lync 11/19/2018 Configuring Quorum Settings Quorum Witness A two node cluster requires a witness for a majority vote The quorum should not be defined on a node This configuration would also require to have a file share location as a resource of the availability group, which would act as one more voter in the quorum. This is needed because we only have two nodes in the availability group, and if one fails, the remaining one can’t have quorum by itself a third party is needed. © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Microsoft Lync 11/19/2018 Configuring Quorum Settings Quorum Witness A two node cluster requires a witness for a majority vote The quorum should not be defined on a node Skype for Business uses a File Share Witness This configuration would also require to have a file share location as a resource of the availability group, which would act as one more voter in the quorum. This is needed because we only have two nodes in the availability group, and if one fails, the remaining one can’t have quorum by itself a third party is needed. © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Microsoft Lync 11/19/2018 Configuring Quorum Settings Quorum Witness A two node cluster requires a witness for a majority vote The quorum should not be defined on a node Skype for Business uses a File Share Witness The File Share should be accessible from both nodes This configuration would also require to have a file share location as a resource of the availability group, which would act as one more voter in the quorum. This is needed because we only have two nodes in the availability group, and if one fails, the remaining one can’t have quorum by itself a third party is needed. © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Microsoft Lync 11/19/2018 Configuring Quorum Settings Quorum Witness A two node cluster requires a witness for a majority vote The quorum should not be defined on a node Skype for Business uses a File Share Witness The File Share should be accessible from both nodes The File Share Witness is configured This configuration would also require to have a file share location as a resource of the availability group, which would act as one more voter in the quorum. This is needed because we only have two nodes in the availability group, and if one fails, the remaining one can’t have quorum by itself a third party is needed. © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Enabling SQL AlwaysOn Configure the SQL instance
AlwaysOn has to be enabled manually If not enabled, an availability group cannot be created

AlwaysOn has to be enabled manually If not enabled, a availability group cannot be created Check “Enable AlwaysOn Availability Groups” on “AlwaysOn High Availability”

A restart of the SQL instance is required

Skype for Business 11/19/2018 5:01 AM Upgrading from SQL Mirroring STEP 5 Create AlwaysOn Availability Group for the existing backend databases Verify the recovery model for each database is set to Full (change to Full if currently set as Simple) Perform a SQL backup of each database Create the new Availability Group and add the existing backend databases © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Skype for Business 11/19/2018 5:01 AM Upgrading from SQL Mirroring STEP 6 Add new SQL Store using the FQDN of the Availability Group Listener In Topology Builder, create New SQL Server Store Add the FQDN of the Availability Group Listener as the SQL Server FQDN Select High Availability Settings, and choose SQL AlwaysOn Availability Groups Add the FQDN of the Availability Group Listener as the FQDN for the SQL Server AlwaysOn Instance © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Skype for Business 11/19/2018 5:01 AM Upgrading from SQL Mirroring STEP 7 Associate the pool with the new SQL Store and publish the topology Change the SQL Server store association for the pool to the new AlwaysOn SQL Store Publish the topology © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

AlwaysOn Availability Groups Known Issues

Issue 1 – Clients go into resiliency mode after fail-over
Skype for Business 11/19/2018 5:01 AM Issue 1 – Clients go into resiliency mode after fail-over RTC Universal groups missing Reason The Availability Group wizard does not replicate the SQL logins from the primary node to each of the defined secondary replicas. Workaround Launch Topology Builder and download topology Verify the SQL machine FQDN value is set to the AG Listener FQDN 2a. If not, change and then publish the topology and wait for CMS replication to occur Use SQL Management Studio to failover the AG Listener cluster resource to one of the replica servers Creates the missing SQL logins on the replica server using PShell Install-CsDatabase –ConfiguredDatabases –SqlServerFqdn {AG Listener fqdn} –ForInstance {instance} –Update Repeat steps 3 – 4 for each additional replica server Note: If you want to create a new database you will need to repoint the SQL Machine FQDN to the Primary Node in the Availability Group © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Issue 2 – CMS blocks upgrade to AlwaysOn
Skype for Business 11/19/2018 5:01 AM Issue 2 – CMS blocks upgrade to AlwaysOn Reason If the CMS database is homed on or paired with the pool where you are attempting to move to AlwaysOn Availability Groups, you will be unable to change the HA model for the backend database Workaround If the pool is not paired, move the CMS database to another pool. Move-CsManagementServer If the pool is paired and the CMS is not homed locally on the pool where you are attempting to change the backend HA model: Disable pool pairing and uninstall the CMS database Change the HA model from SQL mirroring to Availability Groups Reinstall the CMS database and re-enable pool pairing Add the CMS databases to the Availability Group Note: If you want to create a new database you will need to repoint the SQL Machine FQDN to the Primary Node in the Availability Group © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Issue 3 – Cannot create listener - Connection Failure
Skype for Business 11/19/2018 5:01 AM Issue 3 – Cannot create listener - Connection Failure Reason For named instances, SQL Server listens for connections on a dynamic TCP port. Some admins may wish to configure SQL to listen on either the default port (TCP/1433) or use a SQL alias to configure SQL to listen on a non-default static port (e.g., 1499). If you configure your SQL Servers to listen on the default port, you will encounter an error when attempting to create the Availability Group listener for SQL AlwaysOn due to a port conflict Workaround Use a SQL alias to configure SQL to listen on a non-default static port (e.g.,1499) if default SQL port 1433 is already in use ( Verify that exceptions have been added in Windows Firewall for the port used by the Availability Group Listener Note: If you want to create a new database you will need to repoint the SQL Machine FQDN to the Primary Node in the Availability Group © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Issue 4 – Create single replica Availability Group
Skype for Business 11/19/2018 5:01 AM Issue 4 – Create single replica Availability Group Reason For test environments, you may want to create an Availability Group with only a single replica. If you attempt to use SQL Management Studio to do this, you will be blocked as it requires a minimum of two replicas. However, you can use PowerShell to work around this limitation Workaround # Create an in-memory representation of the primary replica $primaryReplica = New-SqlAvailabilityReplica -Name "lab2-sql5\Instance1" -EndpointURL "TCP://lab2-sql5.contoso.com:5022" - AvailabilityMode "SynchronousCommit" -FailoverMode "Automatic" -Version 12 -AsTemplate # Create the Availability Group New-SqlAvailabilityGroup -Name "MyAG" -Path "SQLSERVER:\SQL\lab2-sql5\Instance1" - Database "cpsdyn" # Add additional database to the Availability Group Add-SqlAvailabilityDatabase -Path "SQLSERVER:\SQL\lab2-sql5\Instance1\AvailabilityGroups\MyAG" -Database "rgsconfig" Add-SqlAvailabilityDatabase -Path "SQLSERVER:\SQL\lab2-sql5\Instance1\AvailabilityGroups\MyAG" -Database "rgsdyn" Add-SqlAvailabilityDatabase -Path "SQLSERVER:\SQL\lab2-sql5\Instance1\AvailabilityGroups\MyAG" -Database "rtcab" Add-SqlAvailabilityDatabase -Path "SQLSERVER:\SQL\lab2-sql5\Instance1\AvailabilityGroups\MyAG" -Database "rtcshared" Add-SqlAvailabilityDatabase -Path "SQLSERVER:\SQL\lab2-sql5\Instance1\AvailabilityGroups\MyAG" -Database "rtcxds" # Add Availability Group Listener (note port number - you will get an error if default SQL port 1433 is already in use) New-SqlAvailabilityGroupListener -Name lab2-sqlclu1 -StaticIp ' / ' -Path "SQLSERVER:\SQL\lab2- sql5\Instance1 \AvailabilityGroups\MyAG“ -Port 1431 Note: If you want to create a new database you will need to repoint the SQL Machine FQDN to the Primary Node in the Availability Group © 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11/19/2018 5:01 AM Questions? © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Upgrade and Migration Speaker.

Similar presentations

Presentation on theme: "Upgrade and Migration Speaker."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Upgrade and Migration Speaker.

Similar presentations

Presentation on theme: "Upgrade and Migration Speaker."— Presentation transcript:

Similar presentations

About project

Feedback