After a new installation of Teradata TARA, the first step to configuring the TARA server is defining the Teradata Database system. Refer to Configuring the TARA Server for information on the other steps of configuration. If this is not a new installation of Teradata TARA, there is no required order of configuration.
-
Click .
The TARA Server Configuration dialog box appears with the Teradata tab selected by default.
-
Do one of the following:
-
From the Teradata System list, select the Teradata Database system to configure for the TARA server.
The list contains display names, not TDPID names.
-
Click New to add a Teradata Database system name.
To remove a name from the list, select the name, then click Remove.
-
- In Display Name, type the name that should appear for this TDPID within the Teradata TARA GUI environment. Usually, the display name and the Teradata TDPID name are the same.
- In Teradata TDPID, type the Teradata Database machine name. Usually, the display name and the Teradata TDPID name are the same.
- Enter a Browse user name in Browse User and an associated password in Password; both must be valid within the target Teradata Database. The Browse user and password form the Teradata Database logon information that the TARA server uses to query the Teradata Database.
- Enter an ARC user name in ARC User and an associated password in Password; you must have backup and restore privileges for the ARC User name that you specify. For more details, refer to Teradata Archive/Recovery Utility Reference (B035-2412).
- Click Single stream or Multi stream. For Multi stream, type the number of streams in the Multi stream box. The number of streams is essentially the number of BAR server tape drives that are configured. For example, if there are four BAR servers, each having two tape drives, enter eight streams.
- In Default Session Count, the default for the selected database is set in the Teradata tab of the TARA Server Configuration dialog box (see Step 5 - Configuring NetBackup Information). A general rule is to have one session per amp being archived in the stream. An adequate number of parallel ARC sessions per stream are necessary to keep data moving. Too few sessions cause ARCMAIN to be the bottleneck during archival. Too many sessions are a waste of resources as some of the sessions remain idle. Refer to Teradata Archive/Recovery Utility Reference (B035-2412) for more detail.
- Select the Clients tab of the TARA Server Configuration dialog box, then go to the next step to configure the client systems.