Back Up from Command Line | Teradata AppCenter - Backing Up AppCenter - Teradata AppCenter

Teradata® AppCenter User Guide
Product
Teradata AppCenter
Release Number
1.9
Published
December 2019
Language
English (United States)
Last Update
2019-12-17
dita:mapPath
pkv1559060912029.ditamap
dita:ditavalPath
boe1555608925945.ditaval
dita:id
B035-1111
lifecycle
previous
Product Category
Analytical Ecosystem

"" Administrator

Only users with access to appctl can back up AppCenter. For assistance, contact your IT administrator or Teradata Customer Support.

When you create a backup, AppCenter includes LDAP, system, user, and email configuration. It also includes apps, scripts, and jobs. Backups do not include service accounts. You must recreate the service accounts and assign them to the appropriate apps and scripts after you restore AppCenter.

  1. Log into AppCenter from the command-line interface.
  2. Run the command appctl platform backup --name <backup-file-name> --encKey <backupencKey> --chart <path_chart_bundle> --download --set key1=val1, key2=val2 with the following considerations:
    Parameter Consideration
    --name Required argument that specifies backup file name.
    --chart Required argument that specifies the path to the backup chart bundle (.tgz file).
    --encKey Optional flag that overwrites the default encryption key.
    --download Optional flag that downloads backup to a local /tmp file instead of to a remote file on the cluster.
    -f, --values valueFiles Optional flag that specifies values in YAML file to override chart defaults. You can specify multiple files with each -f flag.
    --set stringArray Optional flag that sets values on the command line. You can specify multiple or separate values with commas. For example:

    key1=val1, key2=val2

    If backup was initiated successfully, a message similar to the following appears:

    Job: <job_name> initiated to take backup with name: backup-file-name.tar.gz.encr

  3. [Optional] To show the status of all backups created during the lifetime of the current platform deployment, run the command appctl platform backup status --filterBy <Success,Failed,Running> with the following consideration:
    Parameter Consideration
    --filterBy Optional flag that filters the backup status command output by the status specified. Status options include:
    • Success
    • Failed
    • Running
    Specify one status option for each run of this command. For example:

    appctl platform backup status --filterBy Success

    Status information for all backups appears. For example:
    Job: <job1> started at <time-1> to take backup with name: <backup-1> has status: Success 
Job: <job2> started at <time-2> to take backup with name: <backup-2> has status: Failed
Job: <job3> started at <time-3> to take backup with name: <backup-3> has status: Running