backup log on DB2 6 to TSM

[*Lakester*]

Hi to everyone,

I have a DB2 v6.1 on a Windows based machine.

I have installed the TSM Client 5.2 on it to backup both the system
and databases.

We've compiled the db2uxt2.cadsm file into the samples\c directory
into the DB2 one and put the executable file into the bin directory.

Enabling UserExit and TrackMod then try to do a full backup of all
databases. Everything is working expect for the logs.
We have also set up the enviroment variables, such as DSMI_DIR,
DSMI_CONFIG and DSMI_LOG.

If I query the TSM server with the db2adutl command I see all the
backup I've done (I've also tried to do an incremental and a delta
backup after the full one) with the correct timestamps but no trace
about logs.

How can I set up DB2 to backup also logs among with data?
We have tried it both on db2 console and control center.

We successfully set up on other Windows/AIX machines with DB2 >= 7.1
and logs are being backupped correctly.

thanks in advance
...
Davide Lakester
ICQ: 40766105

[Ian]

*Lakester* wrote:

Hi to everyone,

I have a DB2 v6.1 on a Windows based machine.

I have installed the TSM Client 5.2 on it to backup both the system
and databases.

We've compiled the db2uxt2.cadsm file into the samples\c directory
into the DB2 one and put the executable file into the bin directory.
I think it's supposed to go in sqllib\adm, not sqllib\bin
Enabling UserExit and TrackMod then try to do a full backup of all
databases. Everything is working expect for the logs.

Stupid question maybe, but I assume that you have LOGRETAIN=YES, too?

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

[*Lakester*]

Ian <ia*****@mobileaudio.com> non sapendo che fare scrisse:

I think it's supposed to go in sqllib\adm, not sqllib\bin

Are we talking about db2uext2 file? the executable one?
Well, I'm sure this file must be in the sqllib/bin directory.

Enabling UserExit and TrackMod then try to do a full backup of all
databases. Everything is working expect for the logs.

Stupid question maybe, but I assume that you have LOGRETAIN=YES, too?

You cannot set LOGRETAIN to YES. The possible values are NO, RECOVERY,
CAPTURE

I set it up to RECOVERY.

...
Davide Lakester
ICQ: 40766105

[Ian]

*Lakester* wrote:

Ian <ia*****@mobileaudio.com> non sapendo che fare scrisse:

I think it's supposed to go in sqllib\adm, not sqllib\bin

Are we talking about db2uext2 file? the executable one?
Well, I'm sure this file must be in the sqllib/bin directory.

This does work, true. However:

sqllib/bin is a soft link to the software installation directory
(/usr/lpp/db2_06_01/bin on AIX), which is common to all instances
on a server. So unless your user exit was modified to be aware
of separate instances (or you've only got one instance), you
could run in to trouble.

sqllib/adm on the other hand is an actual (unique) directory for
each instance, which is why you should put the db2uext2 executable
in this directory.

Enabling UserExit and TrackMod then try to do a full backup of all
databases. Everything is working expect for the logs.

Stupid question maybe, but I assume that you have LOGRETAIN=YES, too?

You cannot set LOGRETAIN to YES. The possible values are NO, RECOVERY,
CAPTURE

RECOVERY == YES. YES is probably deprecated, though.
Anyway: Are you using the sample TSM user exit? It can write to a
couple of log file (USEREXIT.ERR and ARCHIVE.LOG), so you should be
able to see if there are any errors from the TSM api calls. Look at
the source for your user exit to find out where these files are stored.

Also, the db2uext2 binary isn't suid to some other ID, is it? If so,
then the log files would have been stored in TSM under another user ID,
and db2adutl wouldn't be able to see them.


-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

[*Lakester*]

Ian <ia*****@mobileaudio.com> non sapendo che fare scrisse:

This does work, true. However:

sqllib/bin is a soft link to the software installation directory
(/usr/lpp/db2_06_01/bin on AIX), which is common to all instances
on a server. So unless your user exit was modified to be aware
of separate instances (or you've only got one instance), you
could run in to trouble.

sqllib/adm on the other hand is an actual (unique) directory for
each instance, which is why you should put the db2uext2 executable
in this directory.
Yes, you're right!
Now I've moved the db2uext2 file from sqllib\bin to sqllib\adm.

Anyway: Are you using the sample TSM user exit? It can write to a
couple of log file (USEREXIT.ERR and ARCHIVE.LOG), so you should be
able to see if there are any errors from the TSM api calls. Look at
the source for your user exit to find out where these files are stored.
Yes, I'm using TSM user exit sample code.
I've set up the AUDIT_ERROR_PATH to a directory but we get no error
after a backup:

from db2 console:

backup db <dbname> online USE ADSM

Full backup works perfectly but I've tha same problem with logs,
they're not backupped (if I try a db2adult query I see full backups
but no related logs).

Also, the db2uext2 binary isn't suid to some other ID, is it?
Sorry but I didn't get you, what do you mean?

I've compiled db2uext2 on another AIX machine with a C compiler and
root user. Do you mean I've to compile it on this machine where DB2 is
stored and with db2inst1 userid? O__o
If so,
then the log files would have been stored in TSM under another user ID,
and db2adutl wouldn't be able to see them.

...
Davide Lakester
ICQ: 40766105

[*Lakester*]

*Lakester* <la******@tiscalinet.it> non sapendo che fare scrisse:

Ian <ia*****@mobileaudio.com> non sapendo che fare scrisse:

<cut>

I've found the problem :D

It was an api problem, the machine where we compiled it has a more
recent version of tsm api..

thanks for helping anyway

bye


...
Davide Lakester
ICQ: 40766105