NetWorker: NMDA DB2 Triage Guide
Summary: This document outlines the information required to do initial troubleshooting of an NMDA DB2 issue.
Instructions
Information requested for troubleshooting,
1) NetWorker Server and client OS and version
2) NMDA for DB2 version and build number
3) Problem description
- Issue regarding Database Backup
New install?
Yes -> Is the DB2 client created through NMC client create wizard? If not, try to use Wizard and collect outcome.
No -> Was it working before? get
mminfo -avot -r name,savetime,pool,ssflags -q client=<db2 client name>
Does manual backup working?
- Issue regarding Archivelog backup
Log in to DB2 instance with DB2 instance owner
Get output of
db2 get db cfg for <DB name>
Get the DB2 archivelog backup configuration file <db2archive>.cfg file on the DB2 client
4) Error message and log excerpt
5) Backup Device type (Tape, AFTD, Data Domain, VTL or other)
6) Observation: When did it happen, What Changed, How far did the backup progress?
7) Debug:
Set the Debug option in the db2.cfg file
NSR_DEBUG_LEVEL= 1 ~ 9 (most cases 3~5) NSR_DIAGNOSTIC_DEST= /nsr/apps/logs (make the folder full permission to db2 account) NSR_DPRINTF=TRUE (enables NetWorker debug for modules)
8) Logs required:
On NetWorker server - nsrget
On DB2 NetWorker client - nsrget
9) Manual backup Example
UNIX or Linux:
db2 backup db <db name> load /usr/lib/libnsrdb2.so options @/<path/to/db_backup>.cfg> without prompting
Windows:
db2 backup db <db name> load c:\\path\linbsrdb2.dll options @/<path/to/db_backup>.cfg> without prompting
Restore Example.
Restores
On the DB2 host (NetWorker client) where the data is to be restored, type the DB2 restore command appropriate for the operating system as follows:
Linux and UNIX:
$ db2 restore db <source DB name> load /usr/lib/libnsrdb2.xx open sessions <n> options @/pathname/nmdb2.cfg taken at yyyymmddtttt into <target DB name>
Windows:
$ db2 restore db <source DB name> load <drive>:\<NetWorker_Install_Directory>\nsr\bin\libnsrdb2.dll open sessions <n> options @<drive>:\pathname\nmdb2.cfg taken at yyyymmddtttt into <target DB name>