Running an Analyze job enables the TARA application to recognize the backup job. A restore job is created and the archived objects are listed in the restore window of the new TARA server. To run an Analyze job:
-
Record the IOPARM and the ARCHIVE FILEDEF information from the original backup.
For example:
IOPARM = SERVER=barlnx1 POLICY=TD_pol1 CLIENT=barlnx1
DK_gcperf_syscal_archive_DSTREAM0001_<generation_number>
- Using the TARA GUI, create a generic backup job.
-
In the job script:
- Specify the number of job streams. The example sets MULTISTREAM to 1.
- Create a STREAM line for each stream of the original backup. Indicate the server on which the stream will run. In the example below, the stream runs on bsrv3.
-
Using the stream image name from the stream ARC log, create aSTREAMNAME following the STREAM line.
If there are multiple streams, specify all STREAMNAME lines after the STREAM lines. For example:
STREAM 1
STREAM 2
STREAM 3
STREAMNAME 1
STREAMNAME 2
STREAMNAME 3
- Change the script type from Archive to Analyze.
-
Replace the archive script with ANALYZE ALL, VALIDATE, DISPLAY LONG.
JOB DK_analyze_to_create_restore_2 SESSIONS 12 MULTISTREAM 1 STREAM bsrv3 STREAMNAME DK_gcperf_syscal_archive_DSTREAM0001_<generation_number> COMMANDLINE CSNAME=ASCII CHECKSUM=2 TDPID gcperf USERID dbc OTB Tivoli MANAGEMENTCLASS TD_b3_pol1 SCRIPT Analyze LOGON $LOGON; ANALYZE ALL, VALIDATE, DISPLAY LONG, FILE=ARCHIVE; LOGOFF; ENDSCRIPT
-
In the runarctiv.bat located in the home directory of baruser, verify that the client name is the new client name (node).
Comments at the top of the following runarctiv.bat file examples specify CLIENT as the new client.
Windows
@echo off Setlocal rem For analyze only- overriding client. Comment out for normal use set ARCENVX=IOPARM='SERVER=bsrv3 CLIENT=barlnx1'
Linux
#!/bin/bash # For analyze only- overriding client. Comment out for normal use export ARCENVX=IOPARM='SERVER=bsrv3 CLIENT=barlnx1'