Raoul, just to add on to this. Note that those two parameters do not cause anything to happen to the actual images and or objects in the db. They are just anchor pointes to db2 to tell it how far and how much to manage. You could have 20 backup images with num_db_backups set to 5 and rec_his_retentn set to 10 days for example and still be able to restore from your 20th image if you can get your hands on it. It's just that you could not get the proper info from the rec history file. Also note as you've seen that the recovery history file tracks a lot of activity beyond the backup/restore/rollforward. It tracks most tablespace activities. So be carful in pruning! HTH, Pierre. ----- Original Message ----- From: "r x" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, February 05, 2003 7:39 AM Subject: Re: [DB2EUG] NUM_DB_BACKUPS + REC_HIS_RETENTN
> Hi Raoul, > > The size of the recovery history file is controlled by > the rec_his_retentn configuration parameter > that specifies a retention period (in days) for the > entries in the file. Even if the > number for this parameter is set to zero (0), the most > recent full database > backup (plus its restore set) is kept. (The only way > to remove this copy is to > use the PRUNE with FORCE option.) The retention period > has a default value > of 366 days. The period can be set to an indefinite > number of days by using > -1. In this case, explicit pruning of the file is > required. > > Although you can use the PRUNE HISTORY command (see > "PRUNE > HISTORY/LOGFILE" on page 321) at any time to remove > entries from the > history file, it is recommended that such pruning be > left to DB2. The number > of DB2 database backups recorded in the recovery > history file is monitored > automatically by DB2 garbage collection. DB2 garbage > collection is invoked > after a database backup operation completes > successfully; it is also invoked > after a database restore operation completes > successfully. The configuration > parameter num_db_backups defines how many active full > (not incremental) > database backup images are kept. The value of this > parameter is used to scan > the history file, starting with the last entry. > After every full database backup operation, the > rec_his_retentn configuration > parameter is used to prune expired entries from the > history file. > > Your Config says rec_his_retentn is set to 366 days, > and any entries older than 1 year are removed from the > file . > And as for you num_db_backups is concerned, 14 entries > of full DB backup or restores are kept in the recovery > history file and earlier than 14 are removed. > > HTH, > > Ravi. > > Ps. Did your TSM backups / instance owner permissions > issue got resolved ? > > --- [EMAIL PROTECTED] wrote: > > Hi all, > > > > We use DB2 v7.2 on AIX. > > > > For backup we use the following command: > > db2 backup database [db] online use tsm > > > > We remove old backups from TSM as follows: > > db2adutl delete full keep 14 database [db] > > db2adutl delete logs between S[nnn].LOG and > > S[nnn].LOG database [db] > > > > So we only need the last 14 backup's available on > > TSM. > > > > Can you please tell me which values we have to use > > for NUM_DB_BACKUPS and > > REC_HIS_RETENTN? The DB2 documentation is not very > > clear for us at this > > point. > > > > > > Our current values are: > > Number of database backups to retain > > (NUM_DB_BACKUPS) = 14 > > Recovery history retention (days) > > (REC_HIS_RETENTN) = 366 > > > > We don't exactly understand the meaning of the > > REC_HIS_RETENTN value. > > > > Best regards > > > > Raoul Joemman > > Martinair Holland > > > > > > > > > > > ***************************************************************** > > This e-mail and any attachment may contain > > confidential > > and privileged material intended for the addressee > > only. > > If you are not the addressee, you are notified that > > no part of > > the e-mail or any attachment may be disclosed, > > copied or > > distributed, and that any other action related to > > this e-mail > > or attachment is strictly prohibited, and may be > > unlawful. > > If you have received this e-mail by error, please > > notify the > > sender immediately by return e-mail, and delete this > > message. > > Martinair Holland N.V., its subsidiaries and/or its > > employees > > shall not be liable for the incorrect or incomplete > > transmission > > of this e-mail or any attachments, nor responsible > > for any > > delay in receipt. > > > ***************************************************************** > > > > - > > ::: When replying to the list, please use > > 'Reply-All' and make sure > > ::: a copy goes to the list ([EMAIL PROTECTED]). > > *** To unsubscribe, send 'unsubscribe' to > > [EMAIL PROTECTED] > > *** For more information, check > http://www.db2eug.uni.cc > > > __________________________________________________ > Do you Yahoo!? > Yahoo! Mail Plus - Powerful. Affordable. Sign up now. > http://mailplus.yahoo.com > - > ::: When replying to the list, please use 'Reply-All' and make sure > ::: a copy goes to the list ([EMAIL PROTECTED]). > *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] > *** For more information, check http://www.db2eug.uni.cc - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc
