BizTalk Services: Backup and Restore

Important

Microsoft Azure BizTalk Services (MABS) is being retired, and replaced with Azure Logic Apps. If you currently use MABS, then Move from BizTalk Services to Logic Apps provides some guidance on moving your integration solutions to Logic Apps.

If you're brand new to Logic Apps, then we suggest getting started here:

Azure BizTalk Services includes Backup and Restore capabilities. This topic describes how to backup and restore BizTalk Services using the Azure classic portal.

You can also back up BizTalk Services using the BizTalk Services REST API.

Note

Hybrid Connections are NOT backed up, regardless of the Edition. You must recreate your hybrid connections.

Before you Begin

  • Backup and Restore may not be available for all editions. See BizTalk Services: Editions Chart.
  • Using the Azure classic portal, you can create an On Demand backup or create a scheduled backup.
  • Backup content can be restored to the same BizTalk Service or to a new BizTalk Service. To restore the BizTalk Service using the same name, the existing BizTalk Service must be deleted and the name must be available. After you delete a BizTalk Service, it can take longer time than wanted for the same name to be available. If you cannot wait for the same name to be available, then restore to a new BizTalk Service.
  • BizTalk Services can be restored to the same edition or a higher edition. Restoring BizTalk Services to a lower edition, from when the backup was taken, is not supported.

    For example, a backup using the Basic Edition can be restored to the Premium Edition. A backup using the Premium Edition cannot be restored to the Standard Edition.

  • The EDI Control numbers are backed up to maintain continuity of the control numbers. If messages are processed after the last backup, restoring this backup content can cause duplicate control numbers.
  • If a batch has active messages, process the batch before running a backup. When creating a backup (as needed or scheduled), messages in batches are never stored.

    If a backup is taken with active messages in a batch, these messages are not backed up and are therefore lost.

  • Optional: In the BizTalk Services Portal, stop any management operations.

Create a backup

A backup can be taken at any time and is completely controlled by you. This section lists the steps to create backups using the Azure classic portal, including:

On Demand backup

Schedule a backup

On Demand backup

  1. In the Azure classic portal, select BizTalk Services, and then select the BizTalk Service you want to backup.
  2. In the Dashboard tab, select Back up at the bottom of the page.
  3. Enter a backup name. For example, enter myBizTalkServiceBUDate.
  4. Choose a blob storage account and select the checkmark to start the backup.

Once the backup completes, a container with the backup name you enter is created in the storage account. This container contains your BizTalk Service backup configuration.

Schedule a backup

  1. In the Azure classic portal, select BizTalk Services, select the BizTalk Service name you want to schedule the backup, and then select the Configure tab.
  2. Set the Backup Status to Automatic.
  3. Select the Storage Account to store the backup, enter the Frequency to create the backups, and how long to keep the backups (Retention Days):

    Notes

    • In Retention Days, the retention period must be greater than the backup frequency.
    • Select Always keep at least one backup, even if it is past the retention period.
  4. Select Save.

When a scheduled backup job runs, it creates a container (to store backup data) in the storage account you entered. The name of the container is named BizTalk Service Name-date-time.

If the BizTalk Service dashboard shows a Failed status:

Last scheduled backup status

The link opens the Management Services Operation Logs to help troubleshoot. See BizTalk Services: Troubleshoot using operation logs.

Restore

You can restore backups from the Azure classic portal or from the Restore BizTalk Service REST API. This section lists the steps to restore using the classic portal.

Before restoring a backup

  • New tracking, archiving, and monitoring stores can be entered while restoring a BizTalk Service.
  • The same EDI Runtime data is restored. The EDI Runtime backup stores the control numbers. The restored control numbers are in sequence from the time of the backup. If messages are processed after the last backup, restoring this backup content can cause duplicate control numbers.

Restore a backup

  1. In the Azure classic portal, select New > App Services > BizTalk Service > Restore:

    Restore a backup

  2. In Backup URL, select the folder icon and expand the Azure storage account that stores the BizTalk Service configuration backup. Expand the container and in the right pane, select the corresponding back up .txt file.

    Select Open.
  3. On the Restore BizTalk Service page, enter a BizTalk Service Name and verify the Domain URL, Edition, and Region for the restored BizTalk Service. Create a new SQL database instance for the tracking database:

    Select the next arrow.

  4. Verify the name of the SQL database, enter the physical server where the SQL database will be created, and a username/password for that server.

    If you want to configure the SQL database edition, size, and other properties, select Configure Advanced Database Settings.

    Select the next arrow.

  5. Create a new storage account or enter an existing storage account for the BizTalk Service.

  6. Select the checkmark to start the restore.

Once the restoration successfully completes, a new BizTalk Service is listed in a suspended state on the BizTalk Services page in the Azure classic portal.

After restoring a backup

The BizTalk Service is always restored in a Suspended state. In this state, you can make any configuration changes before the new environment is functional, including:

  • If you created BizTalk Service applications using the Azure BizTalk Services SDK, you may need to to update the Access Control (ACS) credentials in those applications to work with the restored environment.
  • You restore a BizTalk Service to replicate an existing BizTalk Service environment. In this situation, if there are agreements configured in the original BizTalk Services portal that use a source FTP folder, you may need to update the agreements in the newly restored environment to use a different source FTP folder. Otherwise, there may be two different agreements trying to pull the same message.
  • If you restored to have multiple BizTalk Service environments, make sure you target the correct environment in the Visual Studio applications, PowerShell cmdlets, REST APIs, or Trading Partner Management OM APIs.
  • It's a good practice to configure automated backups on the newly restored BizTalk Service environment.

To start the BizTalk Service in the Azure classic portal, select the restored BizTalk Service and select Resume in the task bar.

What gets backed up

When a backup is created, the following items are backed up:

Items backed up
Azure BizTalk Services Portal
Configuration and Runtime
  • Partner and profile details
  • Partner Agreements
  • Custom assemblies deployed
  • Bridges deployed
  • Certificates
  • Transforms deployed
  • Pipelines
  • Templates created and saved in the BizTalk Services Portal
  • X12 ST01 and GS01 mappings
  • Control numbers (EDI)
  • AS2 Message MIC values
Azure BizTalk Service
SSL Certificate
  • SSL Certificate Data
  • SSL Certificate Password
BizTalk Service Settings
  • Scale unit count
  • Edition
  • Product Version
  • Region/Datacenter
  • Access Control Service (ACS) namespace and key
  • Tracking database connection string
  • Archiving Storage account connection string
  • Monitoring storage account connection string
Additional Items
Tracking Database When the BizTalk Service is created, the Tracking Database details are entered, including the Azure SQL Database Server and the Tracking Database name. The Tracking Database is not automatically backed up.

Important
If the Tracking Database is deleted and the database needs recovered, a previous backup must exist. If a backup does not exist, the Tracking Database and its data are not recoverable. In this situation, create a new Tracking Database with the same database name. Geo-Replication is recommended.

Next

To create Azure BizTalk Services in the Azure classic portal, go to BizTalk Services: Provisioning Using Azure classic portal. To start creating applications, go to Azure BizTalk Services.

See Also