Filter
Top Products
Integrations with Other Applications
Data Source Integration (DSI)
Chapter 13 645
First select which data you want to log. Data Protector provides a
reporting command omnirpt located in the /opt/omni/bin/
directory. This command can be used to gather various information
about the Data Protector environment. See the omnirpt manpage for
more information on the command. Secondly, write a script that in an
infinite loop queries for the selected data and writes it to standard
output.
2. Create the class specification file.
The class specification file defines what data you want to log and how
you want it to be logged. Data Protector provides a sample class
specification file obdsi.spec in the /etc/opt/omni/dsi directory.
Refer to the DSI manual for the complete syntax of the class
specification file.
3. Compile the class specification file.
Use the sdlcomp command from the /opt/perf/bin directory to
compile the class specification file. In order to compile the Data
Protector sample class specification file, use:
sdlcomp obdsi.spec OmniBack.log OmniBack
4. Configure perflbd.rc
Before you start modifying perflbd.rc file, you have to stop the
mwa services. You do this using the following command:
/opt/perf/bin/mwa stop
Now you can edit the file /var/opt/perf/perflbd.rc. If you are
configuring Data Protector sample metrics, add the following line to
the file. Note that this has to be added as a single line:
DATASOURCE=OMNIBACKII
LOGFILE=/etc/opt/omni/dsi/OmniBack.log
5. Start the logging process.
Start the script that collects your data and pipe its output using
dsilog command. In case of Data Protector sample metrics, use the
following command (in one line):
obdsi.ksh | /opt/perf/bin/dsilog OmniBack.log OMNIBACKII