Is storing archive logs on local disk and backups on vendor storage possible? I am using DB2 9.7.

My LOGARCHMETH1 is set to VENDOR library. Example:

LOGARCHMETH1=VENDOR:/usr/openv/netbackup/bin/nbdb2.sl64


Is it possible to call the following backup command:

db2 backup database EAIBDB2I online \
    load '/usr/openv/netbackup/bin/nbdb2.sl64' \
    without prompting


if I change LOGARCHMETH1 to be on local disk and not on VENDOR library? How should LOGARCHMETH1be specified for that, and do I need other settings?
Yes you should be able to have backups and archived logs go to different places (ie, backups could go to your VENDOR tool and archived logs to disk).

To send archived logs to disk you can do one of two things:

The first would be to set LOGARCHMETH1 to DISK:

db2 "update db cfg using LOGARCHMETH1 'DISK:/dbarch/dblogs'"


The second method would be to have two forms of archiving logs. You can leave LOGARCHMETH1 to your VENDOR and set up LOGARCHMETH2 to point to DISK.

db2 "update db cfg using LOGARCHMETH2 'DISK:/dbarch/dblogs'"


I've not played with two forms of log archiving before, but I know that it is available.

In our company we write our backups and archived logs to disk and then sometime after midnight we have IBM's Tivoli Storage Manager (TSM) come along and take a file system snapshot so it will have a copy of the backups and archived logs. So then we have a backup of our backups. We probably could have worked in LOGARCHMETH2 in our company, but so far this has been simplest for us.

Just giving you ideas of what you can do. :)