Oracle Cloud Infrastructure Documentation

Managing a Backup

Use the Console or the command-line interface to edit, delete, or move a backup. You can also copy a backup to another region.

Validating and Preparing a Backup

Use the Console or the command-line interface to validate and prepare a DB system backup.

Note

You cannot validate and prepare backups of Always Free DB systems.

Use the Console or the command-line interface to edit a backup:

Using the Console

Use the Console to validate and prepare a DB system backup.

  1. On the Backups list page, select the backup that you want to work with. If you need help finding the list page or the backup, see Listing Backups - Using the Console.
    The details page opens and displays information about the backup. Under DB system you can find the details of the associated DB system.
  2. Select Validate at the top of the page.
  3. On the Validate backup panel, you can select Prepare backup to enable backup preparation if the backup has not been prepared previously.
  4. Select Validate.
The backup validation process starts and the backup state transits to Updating. After the validation has completed, you can check the result from the Backup details page.

Using the CLI

Use the command-line interface to validate and prepare a DB system backup.

This task requires the following:
  • A backup OCID.
  • A policy that permits you to validate backups in the compartment or tenancy.
  • A properly configured CLI installation and the requisite SSH keys. See Command Line Interface.
Do the following on the CLI to update a backup:
  1. Open a command prompt, and run the following command:
    oci mysql backup validate 
--backup-id <BackupOCID> 
--is-prepared-backup-required <Boolean>
    • --backup-id: Specify the OCID of the backup.
    • --is-prepared-backup-required: (Optional) Specify whether to prepare the backup. Set to true to prepare the backup. The default is false.
MySQL HeatWave Service validates the backup. It also prepares the backup if enabled.

Editing a Backup

Use the Console or the command-line interface to edit the display name, description, retention period, and soft delete of a DB system backup.

Note

You cannot change the retention period of automatic backups.

The retention period of final backups of Always Free DB systems is limited to a maximum of 7 days.

You cannot change the soft delete of backups of Always Free DB systems.

Use the Console or the command-line interface to edit a backup:

Using the Console

Use the Console to edit the display name, description, and retention period of your backup.

Note

The Edit backup panel is different from the Edit backup plan panel. The Edit backup plan panel enables you to enable automatic backups, edit the retention period and window start time of an existing DB system. See Editing a Backup Plan.
  1. On the Backups list page, select the backup that you want to work with. If you need help finding the list page or the backup, see Listing Backups - Using the Console.

    The details page opens and displays information about the backup. Under DB system you can find the details of the associated DB system.

  2. Select the Details tab.
  3. Select Edit in any of the following field:
    • Name
    • Description
    • Retention days
    • Soft delete
  4. On the Edit backup panel, provide the following details:
    • Display name: Specify the new name of the backup. If you do not modify the name, the existing name is retained.
    • Description: Specify the new description of the backup. If you do not modify the description, the existing description is retained.
    • Retention period: Specify the new retention period of the backup. If you do not modify the retention period, the existing value is retained.
      Note

      You cannot change the retention period of automatic backups.
    • Soft delete: Specify the new soft delete setting. If you do not modify it, the existing setting is retained.
      Note

      When enabled, it retains the backup to be deleted by due to the retention policy in DELETE_SCHEDULED state for 7 additional days before permanently deleting it.
  5. Select Save changes.
The backup metadata is updated.

Using the CLI

Use the command-line interface to update the display name, description, retention period, and soft delete of your backup.

This task requires the following:
  • A backup OCID.
  • A policy that permits you to update backups in the compartment or tenancy.
  • A properly configured CLI installation and the requisite SSH keys. See Command Line Interface.
Do the following on the CLI to update a backup:
  1. Open a command prompt, and run the following command:
    oci mysql backup update 
--backup-id <BackupOCID> 
--display-name <DisplayName>
--description <Description>
--retention-in-days <NumberOfDays>
--soft-delete ENABLED

    • --backup-id: Specify the OCID of the backup.

    • --display-name: (Optional) Specify the new display name of the backup. If you do not define a display name, the existing name is retained.

    • --description: (Optional) Specify the new description of the backup. If you do not define a description, the existing description is retained.

    • --retention-in-days: (Optional) Specify the new number of days to retain the backup. If you do not define a number, the existing retention period is retained.

    • --soft-delete: (Optional) Specify the soft delete setting of the backup, ENABLED or DISABLED.

MySQL HeatWave Service updates the backup metadata.

Editing a Backup Plan

Edit the backup plan of an existing DB system to enable automatic backups, point in time recovery, and soft delete, edit the retention period and window start time, and schedule cross-region backup copy.

Note

You cannot change the backup plan of an Always Free DB system.

Using the Console

Use the Console to edit the backup plan of an existing DB system.

Note

The Edit backup plan panel is different from the Edit backup panel. The Edit backup panel enables you to edit the display name and description of the backup. See Editing a Backup.
  1. On the DB systems list page, select the DB system that you want to work with. If you need help finding the list page or the DB system, see Listing DB Systems - Using the Console.

    The details page opens and displays information about the DB system.

  2. Select the Details tab.
  3. Select Edit in the Automatic backups field under the Backup plan section:
  4. On the Edit backup plan panel:
    Enable automatic backups: Select to enable automatic backups, and to configure the backup retention period, enable point-in-time recovery, and select the backup window. If you do not enable automatic backups, create a manual backup. It is recommended to enable automatic backups.
    • Backup plan:
      • Backup retention period: (Optional) Specify how long to retain the backups, in days. The default retention period is seven days.
      • Enable point-in-time recovery: Select the option to enable you to restore a DB system at a point-in-time to a new DB system.
      • Select backup window: Select to enable you to define the starting time of backup of your DB system in the Window start time field. Your backup starts at some point in the 30 minutes following the Window start time. Select Show backup windows per region to view the default backup window specific to your region.
        Note

        Do not set the backup window start time too near to the maintenance window start time. The automatic backup cannot start if a conflicting operation such as maintenance or upgrade is currently running. It has to wait until the conflicting operation completes. If the conflicting operation does not complete within two hours of the backup window start time, the automatic backup will be skipped and it will try again in the next backup window in the following day.
      • Soft delete: Select to enable soft delete.
      Note

      There is no impact on the DB system or the database connections when the automatic backup is created.
    • Cross-region copy: Select the option to schedule cross-region copy. If enabled, each automatic backup is copied to selected destination region.
      • Destination region: Select a destination region to which the backup is copied.
      • Backup retention period: (Optional) Specify how many days you want to retain the backup in the destination region. If not defined, the default value is the same as the retention period of the source backup.
      Note

      You must have the MYSQL_BACKUP_COPY permission in order to enable cross-region copy. The MYSQL_BACKUP_COPY permission is not included in the mysql-family aggregate resource type. The tenancy must also subscribe to the destination region.
  5. Select Save changes.
The backup plan is updated.

Moving a Backup

You can move an active backup to a different compartment. You can not move a backup that is in any other state.

Note

You cannot move backups of an Always Free DB system to another compartment.

Use the Console or the command-line interface to move a backup to a different compartment.

Using the Console

Use the Console to move your backup to a different compartment.

This task requires the following:
  • The access permission, MYSQL_BACKUP_MOVE, on the compartment to which you want to move your backup. See mysql-backups.
  • An active backup. You can not move a backup that is in any other state.
Do the following to move a backup to a different compartment:
  1. On the Backups list page, select the backup that you want to work with. If you need help finding the list page or the backup, see Listing Backups - Using the Console.

    The details page opens and displays information about the backup. Under DB system you can find the details of the associated DB system.

  2. Select Move resource at the top of the page.
  3. In the Move resource dialog box, choose the new compartment. You cannot select the compartment the backup is currently in.
  4. Select Move backup.
The backup is moved to the selected compartment.

Using the CLI

Use the command-line interface to move a backup to a different compartment.

This task requires the following:
  • A backup OCID.
  • A policy that permits you to move backups in the compartment or tenancy.
  • A properly configured CLI installation and the requisite SSH keys. See Command Line Interface.
Do the following on the CLI to move a backup to a different compartment:
  1. Open a command prompt, and run the following command:
    oci mysql backup change-compartment 
--backup-id <BackupOCID> 
--compartment-id <TargetCompartmentOCID>

    • --backup-id: Specify the OCID of the backup.

    • --compartment-id: Specify the OCID of the target compartment to which the backup is moved.

MySQL HeatWave Service moves the backup to the target compartment.

Exporting a Backup

You can export an active backup to an Object Storage bucket in the same or different compartment in the same tenancy, enabling you to retain your data for an extended period.

The exported backup can then be imported into a new DB system. See Importing Using the Data Import Feature. The exported backup can also be imported fully or partially into an existing DB system. See: Importing Using MySQL Shell. Since the exported backup captures the database's logical structure and data, independent of version-specific data formats, you can import the backup to a lower or higher compatible version of the DB system. You can even use the exported backup for auditing and analytics without having to restore the entire database.

You can initiate only one export for a DB system backup at a time. While the backup export is in progress, you can still use the same backup for restoring the DB system.

You cannot export a backup in the following cases:

  • If the backup is in any state other than active.
  • If the backup has been created on a DB system that contains Lakehouse external tables.

To view the progress of the export, you can navigate to the Object Storage bucket being used for the export, and review the list of objects listed in the Objects tab on the bucket's details page. See Listing Object Storage Objects in a Bucket. You can also monitor the bucket size and number of objects displayed in the Monitoring tab on the bucket's details page. If you notice these values increasing for the last few hours, it indicates that the export is progressing. See Viewing Default Metric Charts for an Object Storage Bucket.

This task requires the following:
  • An active backup. You cannot export a backup that is in any other state.
  • The access permissions, MYSQL_BACKUP_EXPORT and MYSQL_BACKUP_READ, on the compartment from which you want to export your backup. See mysql-backups.
  • The access permissions, BUCKET_INSPECT, BUCKET_READ, OBJECT_CREATE, OBJECT_DELETE, OBJECT_INSPECT, OBJECT_OVERWRITE, and OBJECT_READ, on the compartment containing the Object Storage bucket where you want to export your backup.
  • An Object Storage bucket, in the same tenancy and region as the DB system backup, where you want to export the backup.
  • A subnet with a valid IP address in the region where you want to export the backup, which is used for creating a temporary MySQL instance that is used to export the backup.
Sample Policies
  • To allow any backup to be exported to any Object Storage bucket within the same tenancy:
    ALLOW any-user TO {BUCKET_INSPECT, BUCKET_READ, OBJECT_CREATE, OBJECT_DELETE, OBJECT_INSPECT, OBJECT_OVERWRITE, OBJECT_READ}
IN TENANCY WHERE ALL
{
    request.principal.type = 'mysqlbackup'
}
  • To allow any backup to be exported to any Object Storage bucket in a compartment:
    ALLOW any-user TO {BUCKET_INSPECT, BUCKET_READ, OBJECT_CREATE, OBJECT_DELETE, OBJECT_INSPECT, OBJECT_OVERWRITE, OBJECT_READ}
IN COMPARTMENT <TargetBucketCompartmentOCID> WHERE ALL
{
    request.principal.type = 'mysqlbackup',
    request.principal.compartment.id = '<BackupCompartmentOCID>'
}
  • To allow any backup to be exported to a specific Object Storage bucket:
    ALLOW any-user TO {BUCKET_INSPECT, BUCKET_READ, OBJECT_CREATE, OBJECT_DELETE, OBJECT_INSPECT, OBJECT_OVERWRITE, OBJECT_READ}
IN COMPARTMENT <TargetBucketCompartmentOCID> WHERE ALL
{
    request.principal.type = 'mysqlbackup',
    request.principal.compartment.id = '<BackupCompartmentOCID>',
    target.bucket.name = '<TargetBucketName>'
}
  • To allow a specific backup to be exported to a specific Object Storage bucket:
    ALLOW any-user TO {BUCKET_INSPECT, BUCKET_READ, OBJECT_CREATE, OBJECT_DELETE, OBJECT_INSPECT, OBJECT_OVERWRITE, OBJECT_READ}
IN COMPARTMENT <TargetBucketCompartmentOCID> WHERE ALL
{
    request.principal.type = 'mysqlbackup',
    request.principal.id = '<BackupOCID>',
    request.principal.compartment.id = '<BackupCompartmentOCID>',
    target.bucket.name = '<TargetBucketName>'
}

Use the Console or command-line interface to export your backup to an Object Storage bucket.

Using the Console

Use the Console to export your DB system backup to an Object Storage bucket.

Do the following to export a backup:
  1. On the Backups list page, select the backup that you want to work with. If you need help finding the list page or the backup, see Listing Backups - Using the Console.

    The details page opens and displays information about the backup. Under DB system you can find the details of the associated DB system.

  2. From the Actions drop-down list, select Export backup.
  3. In the Export backup panel, do the following:
    1. In the Object Storage section, do the following:
      1. Specify the name of the compartment and bucket where you want to export the backup.
      2. Specify a new folder name for the exporting the backup. Ensure that a folder with the same name does not already exist in the specified Object Storage bucket.

        If a folder name is not specified, a folder with the name exportbackup<yyyyMMddHHmmss>_<backup_name> is automatically created in the specified Object Storage bucket.

      3. Select the format for storing the exported backup data, which can be CSV or TSV. CSV is selected by default.
    2. In the Compression section, compression is enabled by default.

      To change compression settings, do the following:

      • Select the compression type, which can be ZSDT or GZIP. Compression type ZSDT is selected by default.
        Note

        It is recommended to not use ZSTD with higher compression levels for a large size backup to prevent extended export operation time and potential timeout.
      • Specify the compression level.
        • For ZSDT compression type, compression level ranges from 1 to 22.
        • For GZIP compression type, compression level ranges from 1 to 9.

          Compression level is set to 1 by default.

      To disable compression, turn off Enable backup compression.
    3. If you are exporting a backup that was copied from a different region, you must select a subnet in the current region.

      To select a subnet, do the following in the Configure networking section:

      1. Turn on Enable networking configuration.
      2. Select the virtual cloud network (VCN) compartment and VCN.
      3. Select the subnet compartment and subnet.

      A temporary MySQL endpoint is created in the specified subnet to securely export your backup.

    4. Click Export.
The backup is exported to the specified Object Storage bucket.

Using the CLI

Use the command-line interface to export a backup.

This task requires the following:
  • OCID of an active backup. You cannot export a backup that is in any other state.
  • A properly configured CLI installation and the requisite SSH keys. See Command Line Interface.
Do the following on the CLI to export a backup:
  1. Open a command prompt, and run the following command:
    oci mysql backup export 
    --backup-id <backup_ocid>
    --bucket-name <bucket_name>
    --namespace-name <namespace_name>  
    --subnet-id <subnet_ocid>   
    --export-options 
    "{
        "compressionOptions":
        {
            "isEnabled" : <true_or_false>, 
            "type" : "<compression_type>", 
            "level" : <compression_level>
        },                      
        "folderName" : "<folder_name>",
        "dataFormat": "<data_format>"
    }"

    • --backup-id: Specify the OCID of the active backup that you want to export.

    • --bucket-name: Specify the name of the Object Storage bucket where you want to export the backup.

    • --namespace-name: Specify the Object Storage namespace.
    • --subnet-id: Specify the OCID of the subnet which the temporary MySQL instance is associated with. If not specified, the subnet OCID of the DB system from which the backup is taken is used by default. If you are exporting a backup that was copied from a different region, you must select a subnet in the current region.
    • export-options: Optionally, you can also set the following export options:
      • compressionOptions: Set the following compression options:
        • isEnabled: Specify whether compression is enabled. Default value is true.
        • type: Specify the compression type: ZSDT or GZIP. Default value is ZSDT.
        • level: Specify the compression level. For ZSDT compression type, compression level ranges from 1 to 22. For GZIP compression type, compression level ranges from 1 to 9. Default value is 1.
      • folderName: Specify the name of the folder where you want to store the exported backup. If not specified, a folder with the name exportbackup<yyyyMMddHHmmss_<backup_name> is automatically created in the specified Object Storage bucket.
      • dataFormat: Specify the format used for storing data: TSV or CSV. Default value is CSV.
MySQL HeatWave Service exports the backup.

Canceling the Export of a Backup

If you no longer want an ongoing export of a backup to complete, you can cancel the ongoing export of the backup.

Note

Canceling the export stops the ongoing operation, however, it does not delete the files that have already been exported to the specified Object Storage bucket. If you no longer require the exported files, you must manually delete them from the Object Storage bucket. See: Deleting an Object Storage Object .
This task requires the following:
  • An ongoing export of a DB system backup.
  • The access permissions, MYSQL_BACKUP_EXPORT and MYSQL_INSTANCE_WORK_REQUEST_DELETE, on the compartment from which the backup is being exported. See mysql-backups and mysql-work-requests.

Use the Console or command-line interface to cancel an ongoing export of a backup.

Using the Console

Use the Console to cancel an ongoing export of a backup.

Do the following to cancel an ongiong export of a backup:
  1. On the Backups list page, find the backup that you want to work with. If you need help finding the list page or the backup, see Listing Backups - Using the Console.

    The details page opens and displays information about the backup. Under DB system you can find the details of the associated DB system.

  2. Open the Work requests tab, from the Actions menu of the ongoing export backup work request, select Cancel operation.
  3. On the Cancel export backup dialog box, click Cancel operation.
The export of the backup is canceled.

Using the CLI

Use the command-line interface to cancel the export of a backup.

This task requires a properly configured CLI installation and the requisite SSH keys. See Command Line Interface.
Do the following on the CLI to cancel the export of a backup:
  1. Open a command prompt, and run the following command:
    oci mysql work-request cancel --work-request-id <work_request_ocid>

    • --work-request-id: Specify the OCID of the ongoing export work request.

MySQL HeatWave Service cancels the export of the backup.

Deleting a Backup

Use the Console or the command-line interface to delete a backup of the DB system.

Using the Console

Use the Console to delete a backup of your DB system.

  1. On the Backups list page, find the backup that you want to work with. If you need help finding the list page or the backup, see Listing Backups - Using the Console.
  2. From the Actions menu for the backup, select Delete.
  3. On the Delete backup dialog box, select Delete backup.
The backup is deleted.

Using the CLI

Use the command-line interface to delete a backup.

This task requires the following:
  • A backup OCID.
  • A policy that permits you to delete backups in the compartment or tenancy.
  • A properly configured CLI installation and the requisite SSH keys. See Command Line Interface.
Do the following on the CLI to delete a backup:
  1. Open a command prompt, and run the following command:
    oci mysql backup delete --backup-id <BackupOCID>

    • --backup-id: Specify the OCID of the backup.

MySQL HeatWave Service deletes the backup.

Canceling the Deletion of a Backup

Use the Console or the command-line interface to cancel the deletion of a backup.

Using the Console

Use the Console to cancel the scheduled deletion of a backup.

  1. On the Backups list page, find the backup that you want to work with. If you need help finding the list page or the backup, see Listing Backups - Using the Console.
  2. From the Actions menu for the DB system, select Cancel deletion.
  3. On the Cancel deletion dialog box, select Cancel deletion.
The scheduled deletion of the backup is canceled.

Using the CLI

Use the command-line interface to cancel the deletion of a backup.

This task requires the following:
  • The OCID of a backup that has the DELETE SCHEDULED state.
  • A policy that permits you to cancel the delete of backups in the compartment or tenancy.
  • A properly configured CLI installation and the requisite SSH keys. See Command Line Interface.
Do the following on the CLI to delete a backup:
  1. Open a command prompt, and run the following command:
    oci mysql backup cancel-backup-deletion --backup-id <BackupOCID>

    • --backup-id: Specify the OCID of the backup.

MySQL HeatWave Service cancels scheduled deletion of the backup.

Copying a Backup to Another Region

Copy a backup of the DB system to another region.

Note

You cannot copy backups of an Always Free DB system to another region.

After copying the backup of a DB system to another region, you can restore the DB system in the destination region. It does not copy the configuration of the DB system on which the backup was taken.

When copying DB system backups across regions in your tenancy, the MySQL Maximum Parallel Cross-Region Backup Copy Count service limit determines the maximum number of concurrent copies that you can perform from a specific source region.

This task requires the following:
  • An active backup in any region:
    Note

    You can copy the backup to another region within the same realm in Oracle Cloud Infrastructure. The backup is not currently being copied to the same destination region. You cannot create a copy of the backup in the same region.
  • The access permission, MYSQL_BACKUP_COPY and MYSQL_BACKUP_READ, in the source region where the backup is located in. See mysql-backups.
    Note

    The aggregate resource type mysql-family does not include the MYSQL_BACKUP_COPY permission.
  • The access permission, MYSQL_BACKUP_CREATE, in the destination region where the backup is to be copied to. See mysql-backups.
Sample Policies
  • To allow a group named MyTestGroup1 to copy DB system backups between any regions:
    Allow group MyTestGroup1 to read mysql-backups in tenancy
Allow group MyTestGroup1 to use mysql-backups in tenancy where request.permission = 'MYSQL_BACKUP_COPY'
Allow group MyTestGroup1 to manage mysql-backups in tenancy where request.permission = 'MYSQL_BACKUP_CREATE'
  • To allow a group named MyTestGroup2 to copy DB system backups from the US West (Phoenix) and US East (Ashburn) regions to any destination regions:
    Allow group MyTestGroup2 to read mysql-backups in tenancy
Allow group MyTestGroup2 to use mysql-backups in tenancy where all {request.permission = 'MYSQL_BACKUP_COPY', any {request.region='phx', request.region='iad'})
Allow group MyTestGroup2 to manage mysql-backups in tenancy where request.permission = 'MYSQL_BACKUP_CREATE'
  • To allow a group named MyTestGroup3 to copy DB system backups from the UK South (London) region to the Germany Central (Frankfurt) region:
    Allow group MyTestGroup3 to read mysql-backups in tenancy where request.region = 'lhr'
Allow group MyTestGroup3 to use mysql-backups in tenancy where all {request.permission = 'MYSQL_BACKUP_COPY', request.region = 'lhr', target.destination-region = 'fra'}
Allow group MyTestGroup3 to manage mysql-backups in tenancy where all {request.permission = 'MYSQL_BACKUP_CREATE', request.region = 'fra'}

Use the Console or the command-line interface to copy a backup of the DB system to another region .

Using the Console

Use the Console to copy your backup to another region.

Do the following to copy a backup to another region:
  1. On the Backups list page, select the backup that you want to work with. If you need help finding the list page or the backup, see Listing Backups - Using the Console.

    The details page opens and displays information about the backup. Under DB system you can find the details of the associated DB system.

  2. Select Copy to another region at the top of the page.
  3. On the Copy to another region panel, provide the following details:
    1. Destination region: Select the region to which the backup is copied.
    2. Destination region compartment: The compartment cannot be changed. It always copy to the same compartment.
    3. Display name: (Optional) Specify the name of the backup. The default value is "<SourceBackupName>-copy-from-<SourceRegionName>".
    4. Description: (Optional) Specify the description of the backup. The default value is "This backup is a copy of <SoureBackupName> from the region <SourceRegionName>."
    5. Backup retention period: (Optional) Specify the retention period of the backup in the destination region. The default is the retention period of the source backup.
      Note

      The maximum retention period of an automatic backup is 35 days, the maximum retention period of a manual backup is 365 days.
    6. Encryption key: Select Encrypt using an Oracle-managed key or Encrypt using an customer-managed key.
      If you select a customer-managed key, you need to select one of the following key location:
      • This tenancy: You must first select the Vault and then the Key in the selected vault. You can change the compartment of the vault and key if required.
      • Different tenancy: You must enter the Encryption key OCID.
  4. Select Copy.
The backup is copied to the same compartment in the selected region.
Note

If the COPY_BACKUP work request returns the DbSystemBackupCopyLimitExceeded error, you need to retry the copy backup again at a later time.

Using the CLI

Use the command-line interface to copy a backup of the DB system to another region.

This task requires the following:
  • A source backup OCID.
  • A policy that permits you to read and copy backups in the source region and create backups in the destination region.
  • A properly configured CLI installation and the requisite SSH keys. See Command Line Interface.
    Note

    The CLI must be configured to authenticate with the destination region to which the backup is copied.
Do the following on the CLI to copy a backup of the DB system to another region:
  1. Open a command prompt, and run the following command:
    oci mysql backup copy 
--source-backup-id <SourceBackupOCID> 
--source-region <SourceRegionName>
--compartment-id <DestinationCompartmentOCID> 
--region <DestinationRegionName>
--backup-copy-retention-in-days <NumberOfDays>
--display-name <DisplayName>
--description <Description>

    • --source-backup-id: Specify the OCID of the source backup.

    • --source-region: Specify the region identifier of the source backup. For example:us-ashburn-1, sa-saopaulo-1, and eu-frankfurt-1.

    • --compartment-id: Specify the OCID of the destination compartment to which the backup is copied. It must be same as the compartment of the source backup.

    • --region: (Optional) Specify the destination region identifier to which the backup is copied. If you do not defined the region, the region configured in the CLI config file is used.

    • --backup-copy-retention-in-days: (Optional) Specify the number of days the backup in the destination region is retained. The default retention period is the same as the source backup.

    • --display-name: (Optional) Specify the display name of the copied backup. If you do not define a display name, one is generated for you with the source backup display name.

    • --description: (Optional) Specify the description of the copied backup. If you do not define a description, one is generated for you with the source backup description.

MySQL HeatWave Service starts to copy the source backup to the destination region.