You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/sql-database/sql-database-manage-application-rolling-upgrade.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ manager: craigg
7
7
ms.service: sql-database
8
8
ms.custom: business continuity
9
9
ms.topic: conceptual
10
-
ms.date: 04/01/2018
10
+
ms.date: 08/23/2018
11
11
ms.author: sashan
12
12
13
13
---
@@ -26,10 +26,10 @@ When evaluating the upgrade options you should consider the following factors:
26
26
* Total dollar cost. This includes additional redundancy and incremental costs of the temporary components used by the upgrade process.
27
27
28
28
## Upgrading applications that rely on database backups for disaster recovery
29
-
If your application relies on automatic database backups and uses geo-restore for disaster recovery, it is usually deployed to a single Azure region. In this case the upgrade process involves creating a backup deployment of all application components involved in the upgrade. To minimize the end-user disruption you will leverage Azure Traffic Manager (WATM) with the failover profile. The following diagram illustrates the operational environment prior to the upgrade process. The endpoint <i>contoso-1.azurewebsites.net</i> represents a production slot of the application that needs to be upgraded. To enable the ability to roll back the upgrade, you need create a stage slot with a fully synchronized copy of the application. The following steps are required to prepare the application for the upgrade:
29
+
If your application relies on automatic database backups and uses geo-restore for disaster recovery, it is usually deployed to a single Azure region. In this case the upgrade process involves creating a backup deployment of all application components involved in the upgrade. To minimize the end-user disruption you will leverage Azure Traffic Manager (ATM) with the failover profile. The following diagram illustrates the operational environment prior to the upgrade process. The endpoint <i>contoso-1.azurewebsites.net</i> represents a production slot of the application that needs to be upgraded. To enable the ability to roll back the upgrade, you need create a stage slot with a fully synchronized copy of the application. The following steps are required to prepare the application for the upgrade:
30
30
31
31
1. Create a stage slot for the upgrade. To do that create a secondary database (1) and deploy an identical web site in the same Azure region. Monitor the secondary to see if the seeding process is completed.
32
-
2. Create a failover profile in WATM with <i>contoso-1.azurewebsites.net</i> as online endpoint and <i>contoso-2.azurewebsites.net</i> as offline.
32
+
2. Create a failover profile in ATM with <i>contoso-1.azurewebsites.net</i> as online endpoint and <i>contoso-2.azurewebsites.net</i> as offline.
33
33
34
34
> [!NOTE]
35
35
> Note the preparation steps will not impact the application in the production slot and it can function in full access mode.
@@ -47,7 +47,7 @@ Once the preparation steps are completed the application is ready for the actual
47
47
48
48
If the upgrade completed successfully you are now ready to switch the end users to the staged copy the application. It will now become the production slot of the application. This involves a few more steps as illustrated on the following diagram.
49
49
50
-
1. Switch the online endpoint in the WATM profile to <i>contoso-2.azurewebsites.net</i>, which points to the V2 version of the web site (6). It now becomes the production slot with the V2 application and the end-user traffic is directed to it.
50
+
1. Switch the online endpoint in the ATM profile to <i>contoso-2.azurewebsites.net</i>, which points to the V2 version of the web site (6). It now becomes the production slot with the V2 application and the end-user traffic is directed to it.
51
51
2. If you no longer need the V1 application components so you can safely remove them (7).
@@ -60,7 +60,7 @@ If the upgrade process is unsuccessful, for example due to an error in the upgra
60
60
At this point the application is fully functional and the upgrade steps can be repeated.
61
61
62
62
> [!NOTE]
63
-
> The rollback does not require changes in WATM profile as it already points to <i>contoso-1.azurewebsites.net</i> as the active endpoint.
63
+
> The rollback does not require changes in ATM profile as it already points to <i>contoso-1.azurewebsites.net</i> as the active endpoint.
64
64
>
65
65
>
66
66
@@ -74,12 +74,12 @@ If your application leverages geo-replication for business continuity, it is dep
74
74
* The application remains protected from catastrophic failures at all times during the upgrade process
75
75
* The geo-redundant components of the application are upgraded in parallel with the active components
76
76
77
-
To achieve these goals you will leverage Azure Traffic Manager (WATM) using the failover profile with one active and three backup endpoints. The following diagram illustrates the operational environment prior to the upgrade process. The web sites <i>contoso-1.azurewebsites.net</i> and <i>contoso-dr.azurewebsites.net</i> represent a production slot of the application with full geographic redundancy. To enable the ability to roll back the upgrade, you need create a stage slot with a fully synchronized copy of the application. Because you need to ensure that the application can quickly recover in case a catastrophic failure occurs during the upgrade process, the stage slot needs to be geo-redundant as well. The following steps are required to prepare the application for the upgrade:
77
+
To achieve these goals you will leverage Azure Traffic Manager (ATM) using the failover profile with one active and three backup endpoints. The following diagram illustrates the operational environment prior to the upgrade process. The web sites <i>contoso-1.azurewebsites.net</i> and <i>contoso-dr.azurewebsites.net</i> represent a production slot of the application with full geographic redundancy. To enable the ability to roll back the upgrade, you need create a stage slot with a fully synchronized copy of the application. Because you need to ensure that the application can quickly recover in case a catastrophic failure occurs during the upgrade process, the stage slot needs to be geo-redundant as well. The following steps are required to prepare the application for the upgrade:
78
78
79
79
1. Create a stage slot for the upgrade. To do that create a secondary database (1) and deploy an identical copy of the web site in the same Azure region. Monitor the secondary to see if the seeding process is completed.
80
80
2. Create a geo-redundant secondary database in the stage slot by geo-replicating the secondary database to the backup region (this is called "chained geo-replication"). Monitor the backup secondary to see if the seeding process is completed (3).
81
81
3. Create a standby copy of the web site in the backup region and link it to the geo-redundant secondary (4).
82
-
4. Add the additional endpoints <i>contoso-2.azurewebsites.net</i> and <i>contoso-3.azurewebsites.net</i> to the failover profile in WATM as offline endpoints (5).
82
+
4. Add the additional endpoints <i>contoso-2.azurewebsites.net</i> and <i>contoso-3.azurewebsites.net</i> to the failover profile in ATM as offline endpoints (5).
83
83
84
84
> [!NOTE]
85
85
> Note the preparation steps will not impact the application in the production slot and it can function in full access mode.
@@ -98,7 +98,7 @@ Once the preparation steps are completed, the stage slot is ready for the upgrad
98
98
99
99
If the upgrade completed successfully you are now ready to switch the end users to the V2 version of the application. The following diagram illustrates the steps involved.
100
100
101
-
1. Switch the active endpoint in the WATM profile to <i>contoso-2.azurewebsites.net</i>, which now points to the V2 version of the web site (9). It now becomes a production slot with the V2 application and end-user traffic is directed to it.
101
+
1. Switch the active endpoint in the ATM profile to <i>contoso-2.azurewebsites.net</i>, which now points to the V2 version of the web site (9). It now becomes a production slot with the V2 application and end-user traffic is directed to it.
102
102
2. If you no longer need the V1 application so you can safely remove it (10 and 11).
0 commit comments