Backup BizTalk Service
Updated: January 4, 2016
This topic provides information on how to back up the configuration and all artifacts in the specified BizTalk Services. You must suspend the BizTalk Services before starting the backup using the REST API. For more information, see Suspend BizTalk Service.
Important |
|---|
You cannot backup the Developer or Free editions of BizTalk Services. |
This section provides information about the request operation to back up the specified BizTalk Services.
Method | Request URI | HTTP Version | ||
|---|---|---|---|---|
POST | https://management.core.windows.net/{subscription-id}/cloudservices/{cloud-service-name}/resources/biztalkservices/biztalk/{resource-name}?comp=backup where,
| HTTP/1.1 |
Header | Description |
|---|---|
Content-Type | Required. Set this to application/xml. |
x-ms-version | Required. Specifies the version of the operation to use for this request. The value of this header must be set to 2012-08-01 or later. |
x-ms-client-request-id | Optional. Specifies an ID to identify the request. This can be useful in troubleshooting client issues end-to-end and is passed to the BizTalk Services resource provider. |
If-Match | Optional. If an Etag value is passed for this header for an update operation, Azure matches the value with the Etag for the resource. |
POST https://management.core.windows.net/<subscription-id>}/cloudservices/mycloudservice1/resources/biztalkservices/biztalk/mybiztalkservice?comp=backup HTTP/1.1
Content-Type: application/xml; charset=utf-8
x-ms-version: 2013-04-26
If-Match: {Etag}
<ServiceBackupSettings>
<BackupStoreConnectionString>BlobEndpoint=blobendpoint;QueueEndpoint=queueendpoint;TableEndpoint=tableendpoint;AccountName=accountname;AccountKey=accountkey;DefaultEndpointsProtocol=https</BackupStoreConnectionString>
<BackupName>backup-2012-21-02</BackupName>
</ServiceBackupSettings>
The following table describes the key elements in the request body.
Element Name | Description |
|---|---|
BackupStoreConnectionString | Required. Represents the store in which BizTalk Services backup is created. The specified backup store must already exist. |
BackupName | Required. Represents the backup name which can later be used while restoring the service. You must adhere to the following considerations when providing a backup name:
|
The response includes an HTTP status code, a set of response headers, and a response body.
A successful operation returns status code 202 (ACCEPTED).
For information about status codes, see Service Management Status and Error Codes.
Header | Description |
|---|---|
Content-Type | Specifies the content type. |
x-ms-request-id | A value that uniquely identifies a request made against the application service. |
None.
If there is an error response, the format of the response body is the same as shown at Service Management Status and Error Codes.
This section lists the error codes that you might encounter while performing backup operations on BizTalk Services.
Error Code | Error String | Description |
|---|---|---|
InvalidBackupStore | Backup failed. One or more of the service settings specified are not allowed for backup operation. Please refer to the product documentation on the allowed values and updatable settings. | You might encounter this error when the specified backup store is not a valid Azure storage account. |
InvalidBackupContainer | Backup failed. The backup container in the specified storage account already contains data. Please delete the container or remove all contents inside the container. | - |
InvalidBackupName | Backup failed. Backup name specified is not allowed. Please refer to the product documentation on the allowed values for backup names. | - |
