16.10 - Restoring the Unity Repository from Backup - Teradata Unity

Teradata Unity User Guide

Product
Teradata Unity
Release Number
16.10
Published
January 2018
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
anz1496162519675.ditamap
dita:ditavalPath
ft:empty
Restoring the Unity repository requires a full outage of Unity and reactivating all systems. It is recommended the systems be fully in sync before attempting the restore if possible. Also, both the active and standby repositories must be restored to the same point. Restore only one copy of the repository, and then use the resyncRepository.sh script to copy the restored repository to the standby copy. The Unity repository can be restored using the same backup script. Only this script should be used. Follow these steps:
  1. Deactivate all systems: unityadmin -u admin -P admin -e 'system deactivate system1,system2'
  2. Restore the primary repository using the unityArc.sh script: ./unityArc.sh -r /var/opt/teradata/backup/unity-repository_02_28_14_07_05_09.tar.bz2 -t u14s1 -u dbc -p dbc -P 1026 -d unity
  3. Copy the repository to the Standby repository: /opt/teradata/unity/repository # ./repositorySync.sh
  4. [Optional] If you are not sure about the state of the repository you are restoring, use the optional -fixStates option to reset the state of the repository (this does not affect the data in the repository). To use this option, the cluster must first be shut down.
  5. Check all objects on both system to make sure they are in sync, and then reactivate all systems: unityadmin -u admin -P admin -e 'system activate system1,system2'