- An Episerver cloud account to access the self-services for Episerver DXP. See Creating an Episerver cloud account.
- A provisioned project on DXP.
You can export the CMS or Commerce database to a bacpac file using the API or using the PaaS portal.
When you export a database, it triggers an export job for the requested database. The export job copies the requested database from the requested environment to a new database in the Integration environment. Next, it starts exporting to a bacpac file from the copied database and stores the bacpac in the bacpacs container in the storage of the General environment. Using the General environment reduces the impact on the performance of the requested environment.
If a project does not have a General environment, you should migrate the database using a General environment resource group migration before starting an export job.
Note: The Export Database process can take from a few hours to several days (in extreme cases). You can export only one database at a time.
- Select your project on the home page.
- On the project detail page, open the Troubleshoot tab.
- Scroll down to the Export Database section, select an Environment, Database, and Retention Hours, then click Export.
- Available Database Files. Click Show/Hide to display/hide the files that were exported and not yet expired.
- Expired Database Files. Click Show/Hide to display/hide files that were exported and expired within the last 7 days.
- A confirmation dialog box appears. Click OK to start the export database progress.
The progress result displays in real time, the export database file is shown when the export database progress successfully finishes. (The image shows a new export database process; it’s still running.)
And you have the exported databases at the previous times.
- When you click the database file name, the exported database file is downloaded to your local machine automatically.
Note: You can download the exported database file only when is not expired.
Last updated: Jul 30, 2020