Networker

Re: [Networker] : Backup of DB2 database

2009-10-02 09:38:35
Subject: Re: [Networker] : Backup of DB2 database
From: jee <jee AT ERESMAS DOT NET>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 2 Oct 2009 14:34:26 +0100
Hi Andy,

The error message is not very descriptive. You need to provide more details.
I noticed that the error contains all the oinfo except the server name:

>(server =...<servername>/ client = sanmonitor.patent.gov.uk/ group = db2test)

So, it looks like a config issue. How do you initiate the backup? 

(1) If you can run client initiated DB2 backups ("db2 backup ..." command), 
then check connectivity, DNS,  group configuration for the DB2 client and 
DB2_CFG parameters. (and logs as described below)

(2) If you cannot run DB2 manual backups using the module, then you won't be 
able to run the backup within a group. You will have to work on the client 
side first. Check:
- instance name
- exact backup command and output
- errors in sync with the backup command from:
  *client:
      DB2 (db2diag.log)
      NMDB2 (/nsr/applogs)
 * server
  daemon.log  (/nsr/logs)
-  user of the instance &  name of the instance
-  /etc/hosts on both server and client (modules are much pickier)
-  permissions 


I assume this is a new install and no DB2 backups have run yet. I would 
recommend to rename the logs directory every time you attempt a backup and 
take good note of any changes and current statusd on each attempt just to 
have a consistent set of logs and configuration details. Reading logs from 
different runs where changes have occurred is mission imposible when it comes 
ot DB2/NMDB2. 

On the server: What is the hostname, OS and exact NW version/build?
On the Windows 2003 DB2 client: what are the exact versions of DB2 (db2level) 
and NW (check properties of libnsrdb2.dll or nsrdb2sv binaries) ?

Note: "backing up DB2 on Windows 2003" is a somehow ambiguous but I understand 
Windows 2003 refers to the client. It is better to make this clear specifying 
both client and Nw server OSes.
 
Different versions and combinations of module/server/Nw client may experience 
different symptoms If you can provide all the above details we might be able 
to help.



Regards,
Jee


or are you able to run manual DB2 backups?

 On Friday 02 October 2009 10:10:16 am Andy Williams wrote:
> Hi Guys
>
> Anyone out there backing up DB2 on Windows 2003, we're using Networker V
> 7.4.4 and the networker module for DB2. Normal file level backups are
> working correctly, I just can't get the DB2 side backups running.
>
> If I try to initiate a database backup I get the following message at the
> Networker server end, same message shows in applog.
>
> sanmonitor:DB2:/TPCDB/NODE0000 NMDB2_ERROR: Unable to retrieve backup
> configuration from server. * sanmonitor:DB2:/TPCDB/NODE0000 (server =
> <servername>/ client = sanmonitor.patent.gov.uk/ group = db2test)
>
> No firewall inbetween the two servers, all ports open, I have made the
> database admin and the machine administrator admins at the networker end,
> the correct password is set in the client definition..
>
> Snooping the traffic does'nt show anything useful.
>
> Thanks in advance!
>
>
> Andy
>
>
>
>
>
> To sign off this list, send email to listserv AT listserv.temple DOT edu and 
> type
> "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this
> list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or via RSS at
> http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER