HomeTamr Core GuidesTamr Core API Reference
Tamr Core GuidesTamr Core API ReferenceTamr Core TutorialsEnrichment API ReferenceSupport Help CenterLog In

Azure Backup and Restore

Steps to back up and restore a Tamr Core deployment on Azure.

This topic explains how to back up and restore:

Single-Node Azure Deployment Backup and Restore

Before You Begin:

Configuring a Single-Node Azure HDFS/ADLS2 Backup Location

  1. Configure the following configuration variables using the administration utility:
  1. Optional. Configure the following additional configuration variables using the administration utility:
  • TAMR_BACKUP_FS_EXTRA_URIS
  • TAMR_BACKUP_FS_CONFIG_DIR
  • TAMR_BACKUP_FS_EXTRA_CONFIG
  • TAMR_BACKUP_FS_KERBEROS_ENABLED
  • If TAMR_BACKUP_FS_KERBEROS_ENABLED is set to true, then also configure TAMR_KERBEROS_KEYTAB, TAMR_KERBEROS_PRINCIPAL, and TAMR_KERBEROS_KRB5.
  1. Set TAMR_UNIFY_BACKUP_ES to false. (Elasticsearch backup for Tamr Core on Azure to HDFS/ADLS2 is not currently supported.)
  2. Restart Tamr Core and its dependencies. See Restarting.

Backup Single-Node Azure Deployment

Follow the instructions for single-node Backup.

Restore Single-Node Azure Deployment

Follow the instructions for single-node Restore.

Cloud-Native Azure Deployment Backup and Restore

Before You Begin:

  • Identify the storage account keys for the storage accounts associated with both the HDInsight HBase cluster and the ADLS Gen2 deployment.
  • Verify that the Tamr Core VM instance has network connectivity to both storage accounts.
  • Verify that Tamr Core is deployed following the instructions in Deploying Tamr Core on Azure.

Configuring a Cloud-Native Azure Backup

  1. Define TAMR_UNIFY_BACKUP_HDINSIGHT_STORAGE_ACCOUNT_KEY and TAMR_UNIFY_BACKUP_HDINSIGHT_STORAGE_ACCOUNT_NAME.
  2. Add 'hbase.rootdir':'wasbs://<container>@<account>.blob.core.windows.net/hbase' to TAMR_HBASE_EXTRA_CONFIG where container and storage account are the HDInsight HBase storage account values.
  3. Set TAMR_UNIFY_BACKUP_URI to the ADLS Gen2 https:// path where the backups will be stored.
  4. Set the following properties in TAMR_BACKUP_FS_EXTRA_CONFIG to connect to the ADLS Gen2 deployment to which Tamr will backup:
  • adls.gen2.account.name
  • adls.gen2.container.name
  • adls.gen2.client.id
  • adls.gen2.client.secret
  • adls.gen2.tenant.id
  • adls.gen2.account.key
  1. Set TAMR_UNIFY_BACKUP_ES to false. (Elasticsearch backup for Tamr Core on Azure cloud-native is not currently supported.)

Backup Cloud-Native Azure Deployment

Follow the instructions for single-node Backup.

Restore Cloud-Native Azure Deployment

  1. Complete the prerequisite Restore checklist.
  2. Set TAMR_BACKUP_FS_EXTRA_CONFIG to values for the ADLS Gen2 deployment containing the backup:
  • adls.gen2.account.name
  • adls.gen2.container.name
  • adls.gen2.client.id
  • adls.gen2.client.secret
  • adls.gen2.tenant.id
  • adls.gen2.account.key
  1. Start Tamr Core.
    a. Mount the Tamr Core zip file and updated configuration to the new Tamr Core VM instance.
    b. Set the configuration values. See Creating or Updating a Configuration Variable.
    c. Start Tamr Core and its dependencies. See Restarting.
  2. Restore from backup by running POST /v1/instance/restore. Specify the path to a timestamped backup located at the URI set by the TAMR_UNIFY_BACKUP_URI Tamr Core configuration.
    Note: Tamr Core enters read-only mode for the duration of the restore.
  3. Stop Tamr Core and its dependencies. See Restarting.
  4. Start Tamr Core and its dependencies. See Restarting.
  5. Repopulate Elasticsearch indices.
    Upon restore, the Elasticsearch instance is not automatically restored. Restoring Elasticsearch requires running the re-indexing process, which may take several hours. Consult the Tamr Help Center for details on re-indexing Elasticsearch.

Did this page help you?