Transcript Agenda
Agenda Upgrading to Skype for Business Server 2015 In-place upgrade overview In-place upgrade Upgrade path Upgrade path Role upgrade (2013 to Skype for Business Server 2015) SQL support with Lync / Skype for Business Server Upgrade process Upgrade process STEP 2 STEP 3 STEP 4 STEP 5 Upgrade steps: step 1 Kb2533623 Kb2858668 KB2982006 Upgrade process STEP 2 STEP 3 STEP 4 STEP 5 Upgrade steps: step 2 (Upgrade and publish topology using Topology Builder) Upgrade steps: step 2 (Upgrade and publish topology using Topology Builder) Upgrade process STEP 2 STEP 3 STEP 4 STEP 5 Upgrade process STEP 2 STEP 3 STEP 4 STEP 5 Upgrade process STEP 2 STEP 3 STEP 4 STEP 5 Move towards—Smart Setup Allows Skype for Business Server server updates to be installed as part of Skype for Business Server server setup process from Microsoft Updates Setup will include an option to SQL AlwaysOn Overview Overview AlwaysOn advantages AlwaysOn Availability Groups AlwaysOn Failover Cluster Instance (FCI) SQL AlwaysOn Planning Planning for AlwaysOn SQL version requirements AlwaysOn support information Standalone Failover Clustering Mirroring Availability Groups Supported Availability Group settings SQL in-place upgrade support Windows Server Failover Clustering (WSFC) SQL Server and database requirements High availability option Installation selection Lync 2013 patching 2013 patching and reliability challenges What made 2013 solution problematic? Lync 2013 Skype for Business Skype for Business Server patching Simplified workflow leverages Windows Fabric v2 APIs 4 steps: Invoke-CsComputerFailOver Checks for availability of sufficient number of servers Waits for replica stability across the pool Initiate deactivation of the node; wait for success/failure from windows fabric Stops services after successfully deactivating the node Invoke-CsComputerFailBack Start services if not already started Activate node—windows fabric will now consider this server for replica placement How is this better? How is this better? Notes Pool cold start scenarios Lync 2013/pool cold start problems Skype for Business Server pool start Start-CsPool Summary Q&A Installing the WSFC feature Validating the cluster configuration Creating the cluster Configuring Quorum settings Enabling SQL AlwaysOn Changing the recovery model for each database Performing a full SQL backup for each database Duplicating the database folder structure on replicas AlwaysOn deployment options Deploying AlwaysOn for new pools Deploying AlwaysOn for existing pools Deployment options New pools Creating a new AlwaysOn Availability Group Creating a new AlwaysOn Availability Group Creating a new AlwaysOn Availability Group Creating a new AlwaysOn SQL Store Creating a new AlwaysOn Availability Group Creating a new AlwaysOn Availability Group Creating a new Availability Group Creating a new Availability Group Creating a new AlwaysOn Availability Group Modifying the AlwaysOn SQL Store Deployment options Existing pools Moving from SQL standalone to AlwaysOn Availability Groups Moving from SQL standalone to Availability Groups Moving from SQL standalone to Availability Groups Moving from SQL standalone to Availability Groups Moving from SQL standalone to Availability Groups Moving from SQL standalone to Availability Groups Changing the SQL Server Store association Moving from SQL standalone to Availability Groups Deployment options Existing pools Moving from SQL mirroring to AlwaysOn Availability Groups Moving from SQL mirroring to Availability Groups Moving from SQL mirroring to Availability Groups Moving from SQL mirroring to Availability Groups Moving from SQL mirroring to Availability Groups Moving from SQL mirroring to Availability Groups Moving from SQL mirroring to Availability Groups Moving from SQL mirroring to Availability Groups Moving from SQL mirroring to Availability Groups SQL always on Known issues Issue 1 Clients go into resiliency mode after failing over Availability Group to secondary replica Issue 2 Unable to move from SQL mirroring to AlwaysOn Availability Groups due to location of CMS database Issue 3 Creating an Availability Group with only a single replica Issue 4 Unable to create AlwaysOn Availability Group Listener due to connection failure http://technet.microsoft.com/en-us/library/dn776290.aspx