If you want to restore a backup set to an on-premises database or if you want to save a backup file to on-premises storage or an Excel file for analysis and auditing, you can manually download the backup set. This topic describes how to manually download a backup set.

Feature limits and formats

Limit Logical backup Physical backup
Backup destination storage type Only DBS built-in storage is supported. Object Storage Service (OSS) buckets are not supported.
Note If you store data in OSS buckets, you can download the data in the OSS console. For more information, see Download objects.
Only DBS built-in storage is supported. OSS buckets are not supported.
Note If you store data in OSS buckets, you can download the data in the OSS console. For more information, see Download objects.
Full data The following database engines are supported:
  • MySQL
  • SQL Server
  • MariaDB
  • PostgreSQL
  • PPAS
  • Oracle
  • MongoDB
Note MongoDB data is in the JSON format. Other data is in the CSV format.
The following database engines are supported:
  • MySQL

    In the DBS console, you can download the physical backup sets of self-managed MySQL databases, but not those of ApsaraDB RDS for MySQL instances. You can download the backup sets of ApsaraDB RDS for MySQL instances in the ApsaraDB RDS console. For more information, see Download the backup files of an ApsaraDB RDS for MySQL instance.

  • SQL Server
  • Oracle
Note
  • MySQL data is in the same format as the data in Percona XtraBackup and is compressed.
  • SQL Server data is in the same format as the data generated by the native backup command and is compressed.
  • Oracle data is in the same format as the data backed up in Recovery Manager (RMAN) and is compressed.
Incremental data The following database engine is supported:

MySQL

Note Data is in the native format of MySQL.
The following database engines are supported:
  • MySQL
  • SQL Server
  • Oracle
Note Backup data is in the same format as its full data.

Procedure

  1. Log on to the DBS console.
  2. In the left-side navigation pane, click Backup Schedules. On the Backup Schedules page, select a region in the upper-left corner.
  3. Click the schedule ID or Manage in the Actions column corresponding to a backup schedule.
    Manage button
  4. In the left-side navigation pane of the Configure Task page, choose Backup Tasks > Full Data.
    Note If database engines allow you to download incremental backup data and incremental log backup is enabled for backup schedules, you can also download incremental log backup sets. You can download incremental log backup sets by using the similar method to download full data backup sets. You can choose Backup Tasks > Transaction Log Backup.
  5. Click Download in the Actions column corresponding to a backup set ID.
    Download button
  6. In the dialog box that appears, click OK.

    After you click OK, the system packages, compresses, and converts backup files into downloadable files. The Backup Set Download details page appears. The time it takes to compress and convert a backup file varies with the size of the backup file. The larger the size of the backup file, the longer the time it takes. For example, it takes 4 hours to compress and convert a backup file that has 150 GB of data.

  7. After Completed is displayed in the Status column corresponding to the backup set to be downloaded, click Download.
    Download button 2
  8. In the message that appears, click I see. Downloads to download the backup set to your computer.

    You can also download the backup set from its public or internal endpoint.

    I see. Downloads
  9. After the download is complete, decompress the downloaded package. By default, the backup set is compressed in the <Download task ID>.tar.gz package.

    Run the tar -zxvf <Download task ID>.tar.gz command to obtain the <Download task ID> file.