Download (direct link):
8 - 2 Teradata RDBMS Database Administration
Chapter 8: Archiving, Restoring and Recovering Data
Archive/Recovery (ARC) Utility
Common NetVault Configurations
NetVault with a Teradata plugin can run on UNIX MP-RAS or Windows 2000. NetVault Server without a Teradata plugin can run on any NetVault-supported OS. A non-NCR OS can be a NetVault Master and manage Teradata clients. Many configurations are possible. The more common ones for Teradata sites are summarized below. For full details, see "Choosing System Components and Layout" in NetVault Application Plugin Module User's Guide for Teradata.
IF your NetVault configuration is an .
THEN the NetVault Domain consists of .
SMP system with a single (local) connection
a single TPA node that is:
• Directly connected to a tape library storage device
• Loaded with NetVault Server and a Teradata plugin
• Loaded with Teradata client Tools & Utilities (TTU)
• Selected as the MASTER Teradata plugin machine
MPP system with local (internal) MASTER Teradata plugin
• A TPA node that is the NetVault Server and is:
- Directly connected to the shared tape library
- Loaded with NetVault Server and a Teradata plugin
- Loaded with TTU
- Selected as the MASTER Teradata plugin machine
• One or more TPA nodes that qualify as Slave Teradata plugin machines in a backup system, as long as each is:
- Able to directly access the shared tape library
- Loaded with NetVault Client and a Teradata plugin
- Loaded with the TTU
Note: In this configuration, nodes without direct access to the tape do not need a Teradata plugin. Data is transferred over the BYNET from disconnected nodes to connected nodes.
MPP system with a separate (external) NetVault Server and MASTER Teradata plugin machine
One non-TPA node or network-connected peripheral machine loaded with NetVault Server and functioning as the NetVault Server.
A second non-TPA node, or network-connected peripheral machine, that is:
Selected as the MASTER Teradata plugin machine. Loaded with NetVault Client and a Teradata plugin Loaded with TTU
Connected to the arm controller of a shared tape library
One or more TPA nodes that qualify as Slave Teradata plugin machines in the Backup system, as long as each is: Able to directly access the shared tape library Loaded with NetVault Client and a Teradata plugin Loaded with TTU
8 - 2
Teradata RDBMS Database AdministrationChapter 8: Archiving, Restoring and Recovering Data
Archive or recovery jobs always operate in two phases. The steps of each phase are described below.
Note: The archive process is intensive. You may want to create a user just for archive activities so that you can log on as your administrative user to perform other actions while archive is running.
Phase 1 - Dictionary Phase
1 Allocate an event number.
2 Issue a BEGIN TRANSACTION statement.
3 Resolve object name.
4 Check privileges.
5 Place locks: • Utility locks on data dictionary rows. • Utility locks on data rows.
6 Delete existing tables prior to RESTORE.
7 Issue an END TRANSACTION statement.
Phase 2 - Data Phase
1 Issue a BEGIN TRANSACTION statement.
2 Insert rows into RCEVENT and RCCONFIG.
3 Perform the operation.
4 Update RCEVENT.
5 Release locks (if user specified).
6 Issue an END TRANSACTION statement.
Teradata RDBMS Database Administration
8 - 7Chapter 8: Archiving, Restoring and Recovering Data
Using ARC With Modified PIs or Partitioning
Using ARC With Modified PIs or Partitioning
If you plan to modify PIs with ALTER TABLE (instead of recreating the table) or to use partitioning, consider the following:
• You cannot copy an archive containing tables with PPIs to a Teradata RDBMS that is earlier than V2R5.0.0.
• After completion of a copy or restore involving tables with PPIs, make sure the table headers and partitions are correct by running one of the following:
• LEVEL 3 command of the CheckTable Utility
• REVALIDATE PRIMARY INDEX option of the ALTER TABLE statement. (The ARC command REVALIDATE REFERENCES FOR ... corrects header indexes for RI references that have been marked as inconsistent. For more information on RI and reference indexes, see "Changing the State of RI Tables with REVALIDATE REFERENCES FOR" on page 8-32.)
Note: REVALIDATE PRIMARY INDEX does not correct rows that are out of order by their assigned row ID. If disordered rows occur unexpectedly, contact the TSC as soon as possible.
• The table version number changes when REVALIDATE PRIMARY INDEX corrects partition numbers, or you use MODIFY PRIMARY INDEX to alter the partitioning, uniqueness, or column list of any PI.
A new version or other structural change means you cannot perform the following operations on those tables:
• Cluster restore
• Single AMP restore
• Permanent journal ROLLFORWARD or ROLLBACK
Note: If ARC encounters a table with a changed version during a ROLLBACK or ROLLFORWARD operation, it stops the operation and places an error message in the output listing.