Selective Backup and Restore Rules

Selective Backup and Restore Rules - TARA/ABU

Teradata Archive/Recovery Utility Reference

Product

TARA/ABU

Release Number

16.10

Published

May 2017

Language

English (United States)

Last Update

2018-05-01

dita:mapPath

utr1488824663491.ditamap

dita:ditavalPath

Audience_PDF_include.ditaval

dita:id

B035-2412

lifecycle

Product Category

Teradata Tools and Utilities

When performing a selective backup and restore on a table or database, observe the following rules in order for the operation to be successful.

Methods and UDTs are stored in SYSUDTLIB; SYSUDTLIB is only backed up or restored as part of a DBC backup.
While an operation may be allowed, there is no guarantee the object will function as desired once the operation is complete.
For some copy operations, certain dependencies must be met before the operation can be successful. For example, to copy a database with a journal table — the destination database must be created with a journal table.

Selective Backup and Restore Rules
Type	Restore to same DBS		Copy to same DBS		Copy and Rename to same DBS		Copy to different DBS		Copy and Rename to different DBS
Type	DB Level	Object Level	DB Level	Object Level	DB Level	Object Level	DB Level	Object Level	DB Level	Object Level
Aggregate Function	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes	Yes	No
JAR	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes	Yes	No
External Stored Procedures	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes	Yes	No
Standard Function	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes	Yes	No
Trigger	Yes	Yes	No	No	No	No	No	No	No	No
Instant or Constructor Method	N/A	N/A	N/A	N/A	N/A	N/A	N/A	N/A	N/A	N/A
Join Index	Yes	Yes	Yes	Yes	No	No	Yes	Yes	No	No
System Join Index a	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes	Yes	No
Macro	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes	Yes	No
Hash Index	Yes	Yes	Yes	Yes	No	No	Yes	Yes	No	No
Stored Procedure	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes	Yes	No
Queue Table	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
Table Function	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes	Yes	No
Table Function(Operator)	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes	Yes	No
Table	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
PPI Table	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
NOPI Table	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes	Yes
User-Defined Data Type (UDT)	N/A	N/A	N/A	N/A	N/A	N/A	N/A	N/A	N/A	N/A
View	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes	Yes	No
Authorization	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes	Yes	No
Parser Contract Function	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes	Yes	No
User Installed File (UIF)	Yes	Yes	Yes	Yes	Yes	No	Yes	Yes	Yes	No
Remote Server b c	Yes	Yes	Yes	Yes	No	No	Yes	Yes	No	No
Schema	Yes	Yes	Yes	Yes	No	Yes	Yes b	Yes b	No	Yes b

a. System Join Indexes (SJIs) can be copied to a different database. The DB name can be changed but the object name cannot.

b. All dependent objects used by the remote server or schema object must exist prior to the copy.

c. Remote Server objects must reside in the TD_SERVER_DB database and cannot be copied out to a different database. But, individual objects in the TD_SERVER_DB database can be copied and renamed as long as the Remote Server objects are copied back into the TD_SERVER_DB database.