The Teradata TARA GUI migration feature migrates images created under the legacy Teradata Extension for NetBackup to a Teradata TARA Job Information file. This allows Teradata TARA to restore data from a NetBackup image.
In addition to the Teradata TARA GUI, there is a command-line method that accomplishes the same goal. This method consists of using the NetBackup utility, bplist, and the TARAMigrator command-line utility.
Use the NetBackup utility, bplist, to create a file of image records that will be supplied to the TARAMigrator utility. In the following syntax, parameters enclosed in brackets are optional:
bplist -t 26 [-k <policy_name>] [-s <start_date>] [-e <end_date>] -R /*.0000.B
bplist is piped into the find (Windows) or grep (Linux) command. The output is redirected to a file. For example:
Windows
bplist -t 26 -k TD_pol1 -s 02/28/2007 -e 03/01/2007 -R /*.0000.B | find "0001of" >Migrate.out
Linux
bplist -t 26 -k TD_pol1 -s 02/28/2007 -e 03/01/2007 -R /*.0000.B | grep 0001of > Migrate.out
The file will contain lines such as the following:
barbera.NCR_TD.usr.podin.barac.dat.0001of0002onbarbera.20070327061358.0020.0000.0000.B:\ barbera.NCR_TD.usr.syrah.barac.dat.0001of0002onbarbera.20070327053741.0002.0000.0000.B:\ barbera.NCR_TD.usr.syrah.syscal.dat.0001of0001onbarbera.20070327052222.0000.0000.0000.B:\
Edit the file, removing the :\ (colon backslash) from the end of each line:
barbera.NCR_TD.usr.podin.barac.dat.0001of0002onbarbera.20070327061358.0020.0000.0000.B barbera.NCR_TD.usr.syrah.barac.dat.0001of0002onbarbera.20070327053741.0002.0000.0000.B barbera.NCR_TD.usr.syrah.syscal.dat.0001of0001onbarbera.20070327052222.0000.0000.0000.B
After the file is edited, it is ready for the TARAMigrator utility:
TARAMigrator -u -p -i [-v -P] | -f [-v -P]
-u <username to logon to TARA server> - (required)
-p <password to logon to TARA server> - (required)
OR
-e <path to encoded password file> - (required)
-i <image name> - (required)
-f <image file name> - (required)
-v <verbose level: 0|1|2|3> - (optional)
-P <port> - (optional)
The following table describes TARAMigrator parameters, and indicates if the parameter is required.
| Parameter | Description | Required |
|---|---|---|
| -u <User Name> | Specifies the User Name that the utility uses to connect to the TARA Server. Currently the user names allowed are administrator and user. The user just has the read-only privilege. Example TARAMigrator -u administrator |
Yes |
| -p <password> | Specifies the password for the user name the utility uses to connect to the TARA Server. Example TARAMigrator -u administrator -p xjmT94Rs |
Yes |
| -e <path to encoded password file> | Specifies the path to the file that contains the encoded password to the User Name. Example TARAMigrator -u administrator -e C:\Teradata\tara.pwdThe file containing the encoded password is created during the post-install of the TARA Server, and is located in the TARA server bin directory: \Teradata\TARA\server\bin). The name of the file is tara.pwd. If the utility is running on a machine different from the TARA server, tara.pwd can be copied to the machine, and the path to the file containing the encoded password can be specified. If you need to recreate a file with the encoded password, run the TARALogonGen executable located in the TARA server bin directory: \Teradata\TARA\server\bin. Enter the password and the tool creates a tara.pwd. This file contains the encoded password. |
Yes |
| -P <port> | Specifies the port number that the TARA server is running on. If the TARA Server port is changed to a different number, this option has to be specified with the correct TARA Server port number. Example TaraMigrator -u administrator -p xflu78nS -j MyBackupJob -P 55555The default is 54323. |
No |
| -i<image name> |
This parameter is used if there is only one image that needs to be migrated (as opposed to a file of image names). Specify the -i or the -f option. Do not specify both options in the same command-line. |
Yes |
| -f <file_name> |
This parameter is the file that was created by bplist and edited as described previously. Specify the -i or the -f option. Do not specify both options in the same command-line. |
Yes |
| -v <verbose level: 0|1|2|3> |
This parameter specifies the level of debug information to display. There are three valid debug levels (0, 1, 2, and 3), with higher values providing more extensive debug information. More extensive information is typically only useful for utility developers when gathering information about a reported problem. Level 0 suppresses most debug information, with the exception of some parameter validation errors. Level 1 is the default level if the -v option is not specified. A message is output that indicates the success or failure of the migration operation, including a status line that indicates how many images were migrated and how many failed. If any errors are encountered during the migration, these will be displayed also, with associated error messages. Level 2 provides a low level of debug information collected during the migration process and is typically only useful for utility developers when gathering information about a reported problem. Level 3 provides a higher level of debug information collected during the migration process and is typically only useful for utility developers when gathering information about a reported problem. Example -v 3 Specifying 3 results in the highest level of debug information. Example -v 2 Specifying 2 results in a lower level of debug information. Example -v 0 Specifying 0 results in no debug information. If this parameter is not specified, level 1 is used. |
No |
The verbose level provides diagnostic levels of trace output. Level 0 is useful in scripts where the possible output display of TARAMigrator might not be desired.