編集

次の方法で共有

Exporting databases in the admin center

  • [アーティクル]

From the Business Central administration center, you can export the database for Business Central online environments as BACPAC files to an Azure storage container.

Considerations before you begin

  • You can only request a database export for production environments. If you want to export data from a sandbox environment, you can use Excel or RapidStart.
  • You can only request a database export if the customer has a paid Business Central subscription.
  • You must have explicit permission to export databases. For more information, see the Users who can export databases section.
  • You can't export your database to an Azure premium storage account. The steps in this article are only supported on Azure standard storage accounts.

Note

For each environment, you can export the database a maximum of 10 times per month. You can see the number of exports still remaining for the current month in the Create Database Export pane when creating the export file.

Setting up Azure storage

Before you can export the file, you must first set up the Azure storage account container that the BACPAC file will be exported to.

Creating the storage account

The first step is to create a Standard general-purpose v2 Azure storage account, if you don't already have one. To set up the export, you must first have a subscription to Microsoft Azure and access to the Azure portal.

Important

Exporting an environment database to a storage account that isn't a Standard general-purpose v2 Azure storage account, such as V1 or Premium storage accounts, isn't supported.

For more information setting up an Azure storage account, see Create a storage account.

Generating a shared access signature (SAS)

The next step is to generate a shared access signature (SAS) that provides secure delegated access to your storage account. Business Central uses the signature to write the BACPAC file to your storage account.

To generate a shared access signature (SAS)

  1. On the Azure storage account, choose Shared access signature in the navigation pane.

  2. In the Allowed services section of the shared access signature pane, select Blob, and clear the other options.

  3. In the Allowed resource types section, select Container and Object, and clear the other options.

  4. In the Allowed permissions section, mark Read, Write, Delete, and Create, and clear the other options.

  5. Select a start and end date and time for the SAS. A minimum expiration window of 24 hours from the initiation of the export is required.

    Tip

    It is a best practice to use near-term expiration for the account's SAS. To reduce risk of a compromised storage account, set the end date and time no later than what is needed for you to complete the database export operation. However, the SAS must be valid for a minimum of 24 hours.

  6. In the Allowed protocols section, select HTTPS only.

  7. Select Generate SAS and connection string.

  8. Copy the Blob service SAS URL.

For more information on generating and using a SAS, see Grant limited access to Azure Storage resources using shared access signatures (SAS).

Creating the database export

When you've created the Azure storage account and generated the SAS URI, you can then create the export file from the Business Central administration center.

  1. On the Environments list page, choose the relevant production environment to view the environment details.
  2. On the action ribbon of the environment details, choose Database, and then choose Create Database Export.
  3. In the File Name field, specify a name for the export file, or leave the default value.
  4. In the SAS URI field, specify the Blob service SAS URL value that you copied in the previous section.
  5. In the Container Name field, enter the name of the container in the Azure storage account to which you want the BACPAC file exported. If you've already created a container in your Azure storage account, you can enter the name of that container here. Otherwise, if the name that is specified in the Container Name field doesn't already exist in the Azure storage account, it will be created for you.

Once the export operation begins, the BACPAC file is generated and exported to the indicated Azure storage account. The operation might take several minutes to several hours depending on the size of the database. You can close the browser window with the Business Central administration center during the export. When the export completes, you can access the export file in the defined container in your Azure storage account. Optionally, you can import the data into a new database in Azure SQL Database or SQL Server for further processing. For more information, see Quickstart: Import a BACPAC file to a database in Azure SQL Database.

Viewing the export history

All database export activity is logged for auditing purposes. To view the history, choose Database, then choose View Export History on the environment details page of the environment.

Users who can export databases

Permission to export databases is limited to specific types of users: internal and delegated administrators. The following users are allowed to export databases.

  • Delegated administrators from reselling partners

  • Administrators from the organization that subscribes to Business Central online

Also, these users must have the D365 BACKUP/RESTORE permission set assigned to their user account in the environment they're trying to export.

For more information about permissions sets and user groups, see Assign Permissions to Users and Groups.

Using the exported data

The BACPAC file contains data that is customer-specific business data. Technically, Business Central online is a multitenant deployment, which means that each customer tenant has their own business database while the data that defines the application is in a shared application database.

This means that if you want to export the data in order to change the customer's Business Central from an online deployment to an on-premises deployment, you must also get the application data from the installation media from the same version of Business Central that the online tenant is using. You can see the version number in the Business Central administration center or the Help and Support page in the customer's Business Central.

Important

While you can import the downloaded BACPAC file into your own SQL Server instance, Microsoft does not provide support for creating a working on-premises environment from the BACPAC that you download from Business Central online.

For more information, see Quickstart: Import a BACPAC file to a database in Azure SQL Database, Migrating to Single-Tenancy From Multitenancy, and When to choose on-premises deployment.

Note

If you are getting an error saying your file contains corrupted data when importing the bacpac file please ensure you are using the .NET Core version of SqlPackage.exe.

Restoring the exported data to Business Central online

If you decide at some point that you want to restore the exported data to a new environment in Business Central online, then you must go through the same steps as you went through to migrate from on-premises to Business Central online. This way, you can prepare the database so that it's ready to migrate to the latest version of Business Central. For example, you could choose to replicate the data to a sandbox environment for further testing and training. For more information, see Migrating on-premises data to Business Central online.

Restoring the exported data to a container

If you want to use the exported data in a container-based developer environment, you can use Windows PowerShell scripts to help you do that, including the BCContainerHelper PowerShell module.

SQL Server technical documentation
Quickstart: Import a BACPAC file to a database in Azure SQL Database
Delegated Administrator Access to Business Central Online
Working with Administration Tools
The Business Central Administration Center
Managing Environments
Updating Environments
Managing Tenant Notifications
Introduction to automation APIs