title | description | author | ms.author | ms.service | ms.topic | ms.custom | ms.date |
---|---|---|---|---|---|---|---|
Copy, back up and move your Azure Stream Analytics jobs between regions |
This article describes how to move, copy, and back up an Azure Stream Analytics job. |
su-jie |
sujie |
stream-analytics |
how-to |
subject-moving-resources |
09/11/2019 |
When you want to move, copy or back up your deployed Azure Stream Analytics jobs, you can use the job exporting function in Stream Analytics extension for Visual Studio Code or Visual Studio to achieve. It will help you to export your job's definition to local, then you can backup it there or resubmit it to another region.
Note
- We strongly recommend using Stream Analytics tools for Visual Studio Code for best local development experience. There are known feature gaps in Stream Analytics tools for Visual Studio 2019 (version 2.6.3000.0) and it won't be improved going forward.
- Copying a job to another region does not copy the last output time. Therefore, you cannot use When last stopped option when starting the copied job.
-
If you don't have an Azure subscription, create a free account.
-
Sign in to the Azure portal.
-
Install Azure Stream Analytics extension for Visual Studio Code or Azure Stream Analytics tools for Visual Studio.
-
Click the Azure icon on the Visual Studio Code Activity Bar and then expand Stream Analytics node. Your jobs should appear under your subscriptions.
-
To export a job to a local project, locate the job you wish to export in the Stream Analytics Explorer in Visual Studio Code. Then select a folder for your project.
The project is exported to the folder you select and added to your current workspace.
-
To publish the job to another region or backup using another name, select Select from your subscriptions to publish in the query editor (*.asaql) and follow the instructions.
-
Follow the export a deployed Azure Stream Analytics job to a project instructions.
-
Open the *.asaql file in the Query Editor, select Submit To Azure in the script editor and follow the instructions to publish the job to another region or backup using a new name.