Expanding Teradata Database for Appliance Backup Utility - BAR

Teradata Appliance Backup Utility Installation and User Guide
Product
BAR
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-07-13
dita:mapPath
dhb1488824663275.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-3134
lifecycle
previous
Product Category
Teradata Tools and Utilities
If Teradata Database nodes are added, install ABU and re-configure the existing nodes to synchronize with the new node.
  1. Install ABU software on the new nodes.
  2. Configure the storage devices to match the existing nodes.
  3. Run configure -all to register the new nodes and their storage devices with the ABU server
  4. Run /opt/teradata/abu_service/service/bin/AddNodes.sh. The script asks the user for the BYNET names of the new nodes and copies the existing ABU server repositories to the ABU directories of the new nodes to synchronize ABU on the new nodes with the active ABU server for possible failover recovery.
  5. Existing backup jobs must be either replaced or modified:
    Option Procedure
    Replace backup jobs Use the ABU GUI to create replacement jobs.
    Modify existing backup jobs
    1. Modify the MULTISTREAM line value to match the number of active nodes.
    2. Add a STREAM line for each new node.
    3. Add a DESTINATIONPATH line for each new node.
    In the following example, the boldface entries refer to two nodes added to an existing two-node system:
    JOB Simple_backup
SESSIONS 3
MULTISTREAM 4
STREAM SMP001-8
STREAM SMP001-9
 STREAM SMP002-8 
 STREAM SMP002-9 
COMMANDLINE CSNAME+UTF8
CATALOG ON
TDPID local
USERID dbc
OTB Disk
DESTINATIONPATH /var/abu_storage/disk1
DESTINATIONPATH /var/abu_storage/disk2
 DESTINATIONPATH /var/abu_storage/disk3 
 DESTINATIONPATH /var/abu_storage/disk4 
SCRIPT Archive
LOGON $LOGIN;
ARCHIVE DATA TABLES
    ("SystemFe") ,
RELEASE LOCK,
FILE=ARCHIVE;
LOGOFF;
ENDSCRIPT