You can copy data from one instance of a Teradata Database to another instance of a Teradata Database. With this capability, you can back up a table or database from a production system, then copy that table or database to a test system. In a Disaster Recovery (DR) scenario, you can restore data from a primary production site to a physically separate DR (secondary) site.
The two Teradata Database systems must be connected through TCP/IP to transfer the ABU JobFile, which is a binary file that contains all the information about backup and restore jobs and is located in /var/opt/teradata/abu_service/service/jir. However, the TCP/IP connection is not used or supported for the actual data transfer of the Teradata Database.
Each instance of the Teradata Database must be configured separately, and the Appliance Backup Utility must be installed on both machines. The restore image must also be local to the secondary instance of the Teradata Database.
An image of the data is backed up to and restored from one or two external disks. In the first configuration, external disk storage for the source and target are in separate locations.
In the second configuration, source and target use the same external disk storage. Any dataset images that are deleted must be restored to disk before the data is restored.
To restore to a second instance of the Teradata Database, you will use the Appliance Backup Utility GUI and a command-line interface running on the system to which you will restore data. There are also specific requirements, which are listed in the Restoring Data to a Second Instance procedure. For example, if there are eight streams in the backup job, eight streams are required in the restore job.