Edit BCDR doc

LeoLiMSFT · LeoLiMSFT · commit 7ba33e0853e8 · 2020-04-27T09:17:56.000+08:00
diff --git a/articles/data-factory/configure-bcdr-azure-ssis-integration-runtime.md b/articles/data-factory/configure-bcdr-azure-ssis-integration-runtime.md
@@ -24,114 +24,170 @@ For more info about geo-replication and failover for SQL Database, see [Overview
 
 [!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
 
-## Scenario 1 - Azure-SSIS IR is pointing to read-write listener endpoint
+## Azure-SSIS IR failover with Azure SQL Database Managed Instance
 
-### Conditions
+### Prerequisites
+1. Execute below command on the SSISDB on primary instance. This step is adding a new encryption password.
+```sql
+  ALTER MASTER KEY ADD ENCRYPTION BY PASSWORD = 'password'
+```
 
-This section applies when the following conditions are true:
+2. Create failover group on Azure SQL Database Managed Instance.
 
-- The Azure-SSIS IR is pointing to the read-write listener endpoint of the failover group.
+3. Run **sp_control_dbmasterkey_password** on the secondary instance, using the new encryption password.
+```sql
+  EXEC sp_control_dbmasterkey_password @db_name = N'SSISDB',   
+    @password = N'<password>', @action = N'add';  
+  GO
+```
 
-  AND
+### Solution
+When a failover occurs, if you want to use existing Azure-SSIS IR on primary region:
+1. Stop Azure-SSIS IR on primary region.
 
-- The SQL Database server is *not* configured with the virtual network service endpoint rule.
+2. Edit Azure-SSIS IR with new region, endpoint and VNET information of secondary instance.
 
-### Solution
+```powershell
+  Set-AzDataFactoryV2IntegrationRuntime -Location "new region" `
+                -CatalogServerEndpoint "Azure SQL Database server endpoint" `
+                -CatalogAdminCredential "Azure SQL Database server admin credentials" `
+                -VNetId "new VNet" `
+                -Subnet "new subnet" `
+                -SetupScriptContainerSasUri "new custom setup SAS URI"
+```
 
-When failover occurs, it is transparent to the Azure-SSIS IR. The Azure-SSIS IR automatically connects to the new primary of the failover group.
+3. Restart Azure-SSIS IR.
 
-## Scenario 2 - Azure-SSIS IR is pointing to primary server endpoint
+4. Change the server name in **ConnectionManager** of your SSIS packages with the secondary instance server name, then redeploy these packages and run.
 
-### Conditions
+If you want to provision a new Azure-SSIS IR on secondary region:
+> [!NOTE]
+> Step 4 (creation of IR) needs to be done via PowerShell. Azure portal will report an error stating that SSISDB already exists.
+1. Stop Azure-SSIS IR on primary region.
 
-This section applies when one of the following conditions is true:
+2. Execute stored procedure to update metadata in SSISDB to accept connections from **\<new_data_factory_name\>** and **\<new_integration_runtime_name\>**.
+   
+```SQL
+  EXEC [catalog].[failover_integration_runtime] @data_factory_name='<new_data_factory_name>', @integration_runtime_name='<new_integration_runtime_name>'
+```
 
-- The Azure-SSIS IR is pointing to the primary server endpoint of the failover group. This endpoint changes when failover occurs.
+3. Create a new data factory named **\<new_data_factory_name\>** in the new region. For more info, see Create a data factory.
 
-  OR
+```powershell
+  Set-AzDataFactoryV2 -ResourceGroupName "new resource group name" `
+                      -Location "new region"`
+                      -Name "<new_data_factory_name>"
+```
+  For more info about this PowerShell command, see [Create an Azure data factory using PowerShell](quickstart-create-data-factory-powershell.md)
 
-- The Azure SQL Database server is configured with the virtual network service endpoint rule.
+4. Create a new Azure-SSIS IR named **\<new_integration_runtime_name\>** in the new region using Azure PowerShell.
 
-  OR
+```powershell
+  Set-AzDataFactoryV2IntegrationRuntime -ResourceGroupName "new resource group name" `
+                                           -DataFactoryName "new data factory name" `
+                                           -Name "<new_integration_runtime_name>" `
+                                           -Description $AzureSSISDescription `
+                                           -Type Managed `
+                                           -Location $AzureSSISLocation `
+                                           -NodeSize $AzureSSISNodeSize `
+                                           -NodeCount $AzureSSISNodeNumber `
+                                           -Edition $AzureSSISEdition `
+                                           -LicenseType $AzureSSISLicenseType `
+                                           -MaxParallelExecutionsPerNode $AzureSSISMaxParallelExecutionsPerNode `
+                                           -VnetId "new vnet" `
+                                           -Subnet "new subnet" `
+                                           -CatalogServerEndpoint $SSISDBServerEndpoint `
+                                           -CatalogPricingTier $SSISDBPricingTier
+```
 
-- The database server is a SQL Database Managed Instance configured with a virtual network.
+  For more info about this PowerShell command, see [Create the Azure-SSIS integration runtime in Azure Data Factory](create-azure-ssis-integration-runtime.md)
 
-### Solution
+5. Change the server name in **ConnectionManager** of your SSIS packages with the secondary instance server name, then redeploy these packages and run.
 
-When failover occurs, you have to do the following things:
 
-1. Stop the Azure-SSIS IR.
 
-2. Reconfigure the IR to point to the new primary endpoint and to a virtual network in the new region.
+## Azure-SSIS IR failover with Azure SQL Database
 
-3. Restart the IR.
+### Scenario 1 - Azure-SSIS IR is pointing to read-write listener endpoint
 
-The following sections describe these steps in more detail.
+#### Conditions
+
+This section applies when the following conditions are true:
+
+- The Azure-SSIS IR is pointing to the read-write listener endpoint of the failover group.
+
+  AND
+
+- The SQL Database server is *not* configured with the virtual network service endpoint rule.
+
+#### Solution
+
+When failover occurs, it is transparent to the Azure-SSIS IR. The Azure-SSIS IR automatically connects to the new primary of the failover group.
 
-### Prerequisites
 
-- Make sure that you have enabled disaster recovery for your Azure SQL Database server in case the server has an outage at the same time. For more info, see [Overview of business continuity with Azure SQL Database](../sql-database/sql-database-business-continuity.md).
+### Scenario 2 - Azure-SSIS IR is pointing to primary server endpoint
 
-- If you are using a virtual network in the current region, you need to use another virtual network in the new region to connect your Azure-SSIS integration runtime. For more info, see [Join an Azure-SSIS integration runtime to a virtual network](join-azure-ssis-integration-runtime-virtual-network.md).
+#### Conditions
 
-- If you are using a custom setup, you may need to prepare another SAS URI for the blob container that stores your custom setup script and associated files, so it continues to be accessible during an outage. For more info, see [Configure a custom setup on an Azure-SSIS integration runtime](how-to-configure-azure-ssis-ir-custom-setup.md).
+This section applies when one of the following conditions is true:
+
+- The Azure-SSIS IR is pointing to the primary server endpoint of the failover group. This endpoint changes when failover occurs.
+
+  OR
+
+- The Azure SQL Database server is configured with the virtual network service endpoint rule.
 
-### Steps
 
-Follow these steps to stop your Azure-SSIS IR, switch the IR to a new region, and start it again.
+#### Solution
 
-1. Stop the IR in the original region.
+1. Stop Azure-SSIS IR on primary region.
 
-2. Call the following command in PowerShell to update the IR with the new settings.
+2. Edit Azure-SSIS IR with new region, endpoint and VNET information of secondary instance.
 
-    ```powershell
-    Set-AzDataFactoryV2IntegrationRuntime -Location "new region" `
+```powershell
+  Set-AzDataFactoryV2IntegrationRuntime -Location "new region" `
                     -CatalogServerEndpoint "Azure SQL Database server endpoint" `
                     -CatalogAdminCredential "Azure SQL Database server admin credentials" `
                     -VNetId "new VNet" `
                     -Subnet "new subnet" `
                     -SetupScriptContainerSasUri "new custom setup SAS URI"
-    ```
+```
 
-    For more info about this PowerShell command, see [Create the Azure-SSIS integration runtime in Azure Data Factory](create-azure-ssis-integration-runtime.md)
+3. Restart Azure-SSIS IR.
 
-3. Start the IR again.
+4. Change the server name in **ConnectionManager** of your SSIS packages with the secondary instance server name, then redeploy these packages and run.
 
-## Scenario 3 - Attaching an existing SSISDB (SSIS catalog) to a new Azure-SSIS IR
 
-When an ADF or Azure-SSIS IR disaster occurs in current region, you can make your SSISDB keeps working with a new Azure-SSIS IR in a new region.
-
-### Prerequisites
-
-- If you are using a virtual network in the current region, you need to use another virtual network in the new region to connect your Azure-SSIS integration runtime. For more info, see [Join an Azure-SSIS integration runtime to a virtual network](join-azure-ssis-integration-runtime-virtual-network.md).
+### Scenario 3 - Attaching an existing SSISDB (SSIS catalog) to a new Azure-SSIS IR
 
-- If you are using a custom setup, you may need to prepare another SAS URI for the blob container that stores your custom setup script and associated files, so it continues to be accessible during an outage. For more info, see [Configure a custom setup on an Azure-SSIS integration runtime](how-to-configure-azure-ssis-ir-custom-setup.md).
+When an ADF or Azure-SSIS IR disaster occurs in current region, you can make your SSISDB keeps working with a new Azure-SSIS IR in a new region.
 
-### Steps
+#### Solution
 
-Follow these steps to move your Azure-SSIS IR to a new region.
 > [!NOTE]
-> Step 3 (creation of IR) needs to be done via PowerShell. Azure portal will report an error stating that SSISDB already exists.
+> Step 4 (creation of IR) needs to be done via PowerShell. Azure portal will report an error stating that SSISDB already exists.
+
+1. Stop Azure-SSIS IR on primary region.
 
-1. Execute stored procedure to update metadata in SSISDB to accept connections from **\<new_data_factory_name\>** and **\<new_integration_runtime_name\>**.
+2. Execute stored procedure to update metadata in SSISDB to accept connections from **\<new_data_factory_name\>** and **\<new_integration_runtime_name\>**.
    
-  ```SQL
-    EXEC [catalog].[failover_integration_runtime] @data_factory_name='<new_data_factory_name>', @integration_runtime_name='<new_integration_runtime_name>'
-   ```
+```SQL
+  EXEC [catalog].[failover_integration_runtime] @data_factory_name='<new_data_factory_name>', @integration_runtime_name='<new_integration_runtime_name>'
+```
 
-2. Create a new data factory named **\<new_data_factory_name\>** in the new region. For more info, see Create a data factory.
+3. Create a new data factory named **\<new_data_factory_name\>** in the new region. For more info, see Create a data factory.
 
-     ```powershell
-     Set-AzDataFactoryV2 -ResourceGroupName "new resource group name" `
+```powershell
+  Set-AzDataFactoryV2 -ResourceGroupName "new resource group name" `
                          -Location "new region"`
                          -Name "<new_data_factory_name>"
-     ```
-    For more info about this PowerShell command, see [Create an Azure data factory using PowerShell](quickstart-create-data-factory-powershell.md)
+```
+  For more info about this PowerShell command, see [Create an Azure data factory using PowerShell](quickstart-create-data-factory-powershell.md)
 
-3. Create a new Azure-SSIS IR named **\<new_integration_runtime_name\>** in the new region using Azure PowerShell.
+4. Create a new Azure-SSIS IR named **\<new_integration_runtime_name\>** in the new region using Azure PowerShell.
 
-    ```powershell
-    Set-AzDataFactoryV2IntegrationRuntime -ResourceGroupName "new resource group name" `
+```powershell
+  Set-AzDataFactoryV2IntegrationRuntime -ResourceGroupName "new resource group name" `
                                            -DataFactoryName "new data factory name" `
                                            -Name "<new_integration_runtime_name>" `
                                            -Description $AzureSSISDescription `
@@ -146,11 +202,12 @@ Follow these steps to move your Azure-SSIS IR to a new region.
                                            -Subnet "new subnet" `
                                            -CatalogServerEndpoint $SSISDBServerEndpoint `
                                            -CatalogPricingTier $SSISDBPricingTier
-    ```
+```
+
+  For more info about this PowerShell command, see [Create the Azure-SSIS integration runtime in Azure Data Factory](create-azure-ssis-integration-runtime.md)
 
-    For more info about this PowerShell command, see [Create the Azure-SSIS integration runtime in Azure Data Factory](create-azure-ssis-integration-runtime.md)
+5. Change the server name in **ConnectionManager** of your SSIS packages with the secondary instance server name, then redeploy these packages and run.
 
-4. Start the IR again.
 
 ## Next steps
 
