About Appliance Backup Utility Configuration - BAR

Teradata Appliance Backup Utility Installation and User Guide
Product
BAR
Release Number
16.20
Published
November 2017
Language
English (United States)
Last Update
2018-07-13
dita:mapPath
myx1512701901323.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-3134
Product Category
Teradata Tools and Utilities

Standard Configuration

In a standard configuration, the server, client, and GUI reside on one Teradata Database node and clients reside on the remaining Teradata Database nodes in the system. For best performance, connect each Teradata Database node to disk storage. Each storage destination must have enough capacity to store a client stream's data. If the destination becomes full before all data in the stream has been backed up, the backup job aborts.

For multi-node systems, the Application Backup Utility uses the public network interface to communicate between the Application Backup Utility server and Application Backup Utility clients, and maps BYNET aliases to established SMPxxx-yy host aliases. For example, SMP001-6 is the public network interface and byn001-6 is the BYNET interface for the same node.
You can install the GUI on any node that is connected to the Appliance Backup Utility server. The Application Backup Utility server and GUI software is automatically configured on the node when you run the configuration script. The configuration script also establishes and registers each client with the server.
Appliance Backup Utility Software

Disk storage device capacity must be greater than the size of the Teradata Database that you are backing up. During the backup process, a stream writes to only one storage device path. If the storage device reaches its capacity limit, the stream will fail.

Customized Configuration

The Appliance Backup Utility is designed to use all Teradata Database nodes in the Teradata Database system, but you can configure the Appliance Backup Utility to use a subset of the Teradata Database nodes. For example, if you have eight Teradata Database nodes but only four nodes are connected to disk storage, configure the Appliance Backup Utility to use the four Teradata Database nodes that are connected to disk storage.

Backup and restore performance is degraded when Appliance Backup Utility client software is not installed on every node and disk storage is not connected to every node. Teradata Corporation does not recommend this configuration.

Performance and Teradata Database

Appliance Backup Utility performance depends on the Teradata Database platform your system uses.

Performance information is frequently tuned and updated, so please consult with your sales representative for most current information from Appliance Infohub, an internal Teradata Corporation website.

Local AMP for Improved Performance

To improve backup and restore job performance, Teradata ARC optimizes local sessions when assigning AMPs. The process requires that Teradata ARC must be able to log onto a MONITOR session to determine AMP location. Grant the MONITOR privilege to the Teradata user logon that was specified when the configuration script was run.

  • Use the BTEQ utility to grant the privilege.
  • Use GRANT MONITOR TO < arcuser >, where <arcuser> is the user name specified in the configuration script.