Restore Backup to New Instance Fails with "Manifest File was Not Found" Error

Problem: In Tamr version 2020.016, the backup manifest changed from a json file to a yaml file to support GCP native backup and restore.

If a user attempts to restore a v2020.016.2, v2020.016.1, or v2020.016.0 backup on v2020.016.3 or v2020.016.4 releases, the restore fails with the error message that the “Manifest file was not found”.

Version affected: v2020.016.3 and v2020.016.4

Workaround: Create a manifest.yaml based on this example, replacing the ElasticSearch directory with the directory from the backup:

    tamrVersion: 2020.016.4

    startTime: 1605215567

    startTimestamp: 2020-11-12_21-12-47-337

    initiatedByUser: admin

    contents:

    elasticsearch:
      relativePath: elasticsearch/956ffdd9-5895-41fd-9539-e2ee8c22159b

    tamrFiles:
      relativePath: files

    hbaseExport:
      relativePath: hbase

    postgresqlDump:
      relativePath: database/pg_dump.out

    tamrConfig:
      relativePath: config/config.json

    tamrUpgradeStatus:
      relativePath: upgradeStatus/upgradeStatus.json 

Did this page help you?