Skip to content

Commit bf2ef25

Browse files
committed
AZ Migration Guidance: Azure Cognitive Search
1 parent b7a998d commit bf2ef25

File tree

1 file changed

+59
-0
lines changed

1 file changed

+59
-0
lines changed
Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
---
2+
3+
title: Migrate Azure Cognitive Search to availability zone support
4+
description: Learn how to migrate Azure Cognitive Search to availability zone support.
5+
author: mattmsft
6+
ms.service: azure
7+
ms.topic: conceptual
8+
ms.date: 08/01/2022
9+
ms.author: magottei
10+
ms.reviewer: mcarter
11+
ms.custom: references_regions
12+
13+
---
14+
15+
# Migrate Azure Cognitive Search to availability zone support
16+
17+
This guide describes how to migrate Azure Cognitive Search from non-availability zone support to availability support.
18+
19+
Azure Cognitive Search services can take advantage of availability support [in regions that support availability zones](../search/search-performance-optimization.md#availability-zones). Services with [two or more replicas](../search/search-capacity-planning.md) in these regions created after availability support was enabled can automatically utilize availability zones. Each replica will be placed in a different availability zone within the region. If you have more replicas than availability zones, the replicas will be distributed across availability zones as evenly as possible.
20+
21+
If a search service was created before availability zone support was enabled in its region, the search service must be recreated to take advantage of availability zone support.
22+
23+
## Prerequisites
24+
25+
The following are the current requirements/limitations for enabling availability zone support:
26+
27+
- The search service must be in [a region that supports availability zones](../search/search-performance-optimization.md#availability-zones)
28+
- The search service must be created after availability zone support was enabled in its region.
29+
- The search service must have [at least 2 replicas](../search/search-performance-optimization.md#high-availability)
30+
31+
## Downtime requirements
32+
33+
Downtime will be dependent on how you decide to carry out the migration. Migration will consist of a side-by-side deployment where you'll create a new search service. Downtime will depend on how you choose to redirect traffic from your old search service to your new availability zone enabled search service. For example, if you're using [Azure Front Door](../frontdoor/front-door-overview.md), downtime will be dependent on the time it takes to update Azure Front Door with your new search service's information. Alternatively, you can route traffic to multiple search services at the same time using [Azure Traffic Manager](../traffic-manager/traffic-manager-overview.md).
34+
35+
## Migration guidance: Recreate your search service
36+
37+
### When to recreate your search service
38+
39+
If your search service was was created in a region that supports availability zones before this support was enabled, the search service needs to be recreated.
40+
41+
### How to recreate your search service
42+
43+
1. [Create a new search service](../search/search-create-service-portal.md) in the same region as the old search service. This region should [support availability zones on or after the current date](../search/search-performance-optimization.md#availability-zones). The [free and basic tiers do not support availability zones](../search/search-sku-tier#feature-availability-by-tier), so they should not be used.
44+
1. Add at [least 2 replicas to your new search service](..search/search-capacity-planning.md#add-or-reduce-replicas-and-partitions). Once the search service has at least 2 replicas, it automatically takes advantage of availability zone support.
45+
1. Migrate your data from your old search service to your new search service. This requires a complete rebuild of all your search indexes from your old service.
46+
1. You can [move individual indexes from your old search service to your new one](https://github.com/Azure-Samples/azure-search-dotnet-samples/tree/master/index-backup-restore), or you can rebuild indexes from an external data source if one is available.
47+
1. Redirect traffic from your old search service to your new search service. This may require updates to your application that uses the old search service.
48+
1. Services such as [Azure Front Door](../frontdoor/front-door-overview.md) and [Azure Traffic Manager](../traffic-manager/traffic-manager-overview.md) help simplify this process.
49+
50+
## Next steps
51+
52+
> [!div class="nextstepaction"]
53+
> [Learn how to create and deploy ARM templates](../azure-resource-manager/templates/quickstart-create-templates-use-visual-studio-code.md)
54+
55+
> [!div class="nextstepaction"]
56+
> [ARM Quickstart Templates](https://azure.microsoft.com/resources/templates/)
57+
58+
> [!div class="nextstepaction"]
59+
> [Learn about high availability in Azure Cognitive Search](../search/search-performance-optimization.md)

0 commit comments

Comments
 (0)