DB2 - Archive Mode - on what values to set LOGPRIMARY,LOGSECOND,LOGFILSIZ? we must set our database from CIRCULAR to ARCHIVE mode in order to enable ONLINE backups.
Backups will be done every 1 day.
Database is now almost 30GB.
Database grows approximately  1GB per month.
For online backup we will use Veritas NetBackup so we use its library file in the LOGARCHMETH1 parameter for the VENDOR option.
Time to restore is not so important parameter, it is important to everything restore from previous day when everything was OK.

Can you please assist me to set those three parameters on appropriate value? This is production database with important data.

LOGPRIMARY and LOGSECOND are set to values 13 and 15 by default but I think it is not enough? Is it to large if I set them to 50 for example? What can be negative effect?

Current values are: 13, 15, 4096.
I run Configuration Advisor and it gives me those values: 27, 7, 1024.
But for many wizard questions I used default values because I do not know exact answers (for example Transactions per minute,or Average number of connected remote applications..)
Why it put the lower value for LOGFILSIZ?

Can someone additionally suggest me are those good values or not ?
Thank you!!!!
LOGPRIMARY, LOGSECOND and LOGFILSIZ combine to define the maximum size of the transaction log on your server using the following formula:

Total Size = (LOGPRIMARY + LOGSECOND) * LOGFILSIZ * 4096 bytes


In your case, this results in (13 + 15) * 4096 * 4096 = 469762048 bytes.

The maximum transaction log size limits 2 things:

1) the absolute size of a single transaction
2) the "timespan" between the oldest active transaction and the newest transaction.

You need to make it large enough to handle both scenarios, although if you're running into problems relating to #2 then you really have a problem with a poorly-behaved app that isn't committing.

Choosing an appropriate value for LOGFILSIZ should be based on how regularly you want to archive log files, as this will have an effect on your recoverability in the event of a problem.  If your database archives log files only once every hour (or less), you will potentially lose much more data in the event of a serious problem than if your database archives a log file every 2-3 minutes (because every time a log file is archived it should be copied to NetBackup).