aptible backup:restore

πŸ“˜

Tip

backup:restore creates a new database: it does not overwrite your existing database. In fact, it doesn't interact with your existing database at all.

This command is used to restore from a Database Backup.

You'll need the ID of an existing Backup to use this command. You can find those IDs using the aptible backup:list command, or through the Dashboard.

❗

️ Warning

If you are restoring a Backup of a GP3 volume, the new Database will be provisioned with the base performance characteristics: 3,000 IOPs and 125MB/s throughput. If the original Database's performance was scaled up, you may need to modify the restored Database if you wish to retain the performance of the source Database.

Examples

Restore a Backup

aptible backup:restore "$BACKUP_ID"

Customize the new Database

You can also customize the new Database that will be created from the Backup:

aptible backup:restore "$BACKUP_ID" \
        --handle "$NEW_DATABASE_HANDLE" \
        --container-size "$CONTAINER_SIZE_MB" \
        --size "$DISK_SIZE_GB"

Restore to a different Environment

You can restore Backups across Environments as long as they are hosted on the same Stack:

aptible backup:restore "$BACKUP_ID" \
        --environment "$ENVIRONMENT_HANDLE"

Synopsis

Usage:
  aptible backup:restore BACKUP_ID [--environment ENVIRONMENT_HANDLE] [--handle HANDLE] [--container-size SIZE_MB] [--disk-size SIZE_GB] [--key-arn KEY_ARN]

Options:
  [--handle=HANDLE]            # a name to use for the new database
  [--environment=ENVIRONMENT]  # a different environment to restore to
  [--container-size=N]
  [--size=N]
  [--disk-size=N]
  [--key-arn=KEY_ARN]

Restore a backup

Did this page help you?