Upgrading Service Bus from Previous Releases

  • [アーティクル]

 

Applies To: Service Bus for Windows Server 1.1

This section describes the procedure required to upgrade a Service Bus for Windows Server farm from previous releases of Service Bus for Windows Server.

Service Bus for Windows Server 1.1 supports upgrading from Service Bus for Windows Server 1.0, or from Service Bus for Windows Server 1.0 Cumulative Update 1 (CU1).

Note

Service Bus for Windows Server 1.1 does not support upgrading farms used for Workflow Manager 1.0.

Note

Prior to the migration of a Service Bus for Windows Server farm, it is strongly recommended that you back up the farm’s databases. When running the Invoke-SBFarmUpgrade cmdlet, there is no way to roll back.

Note

During the upgrade, you are asked to provide the connection string to the management database as well as the farm’s certificate auto generation key. In order to retrieve the database connection string, you can call the Get-SBFarm cmdlet. While you cannot extract the certificate auto generation key, you can change it by calling the Set-SBCertificateAutoGenerationKey cmdlet.

To upgrade a Service Bus farm

  1. Stop the Service Bus for Windows Server farm: from a PowerShell console window, call the Stop-SBFarm cmdlet

  2. On each of the farm nodes, leave the farm. From a PowerShell console window, call the Remove-SBHost cmdlet.

  3. On each of the farm nodes, uninstall Service Bus for Windows Server 1.0. From Add/Remove Programs in Control Panel, uninstall Service Bus for Windows Server 1.0 (or Service Bus for Windows Server 1.0 CU1). Note that there is no need to uninstall Windows Fabric.

  4. On each of the farm nodes, install Service Bus for Windows Server 1.1 using the Web Platform Installer.

  5. From one of the farm nodes, upgrade the farm’s databases. Call the Invoke-SBFarmUpgrade cmdlet and provide a connection string to your management database as well as the certificate auto generation key.

  6. On each of the farm nodes, join the farm by using either the configuration wizard, or the Add-SBHost cmdlet.

  7. To join a Windows Azure Pack management portal, use the Set-SBFarm cmdlet to add the resource provider credentials for admin and tenant. Note that you must deploy the Windows Azure Pack first.

  8. In the Windows Azure Pack management portal, you may want to associate existing namespaces with WAP subscriptions. Call the Set-SBNamespace cmdlet and add a subscriptionID value to existing namespaces.