ADSM-L

Re: delete DB2 backups and logs

2003-05-16 13:54:35
Subject: Re: delete DB2 backups and logs
From: Kurt Beyers <kurt.beyers AT PANDORA DOT BE>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 16 May 2003 19:43:51 +0200
In the Redbook they say that you should use the value RETVAL=NOLIMIT for the
DB2 logs.

But it makes more sense to me that if you want to keep 3 full backups (full
backup each weekend, incremental during the week) that a RETVAL=22 days (3
weeks + 1 extra day) should be used. Or am I wrong here?

Kurt

----- Original Message -----
From: "Bill Boyer" <bill.boyer AT VERIZON DOT NET>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Friday, May 16, 2003 4:31 PM
Subject: Re: delete DB2 backups and logs


> The redbook "Backing up DB2 with TSM" has examples of scripts for AIX for
> doing the expiration as well as the management class retentions you'll
need.
>
> For syncronizing the history with it that would depend on your retention
of
> the bakcups with the DB2ADUTL utility. Set the database attributes: (DB2
GET
> DB CFG FOR <database>)
>
>  Number of database backups to retain   (NUM_DB_BACKUPS) = 30
>  Recovery history retention (days)     (REC_HIS_RETENTN) = 60
>
> According to one of the DB2 manuals I read through, after the completion
of
> a full backup DB2 will automatically prune the history file based on these
> parameters. I think it was referred to as garbage collection. But don't
> quote me on that! :-)  Since this server of our does a full every day
there
> is a months' worth of backup information kept in the history file. And any
> history records older that 60-days are pruned that don't need to be kept
due
> to a backup that hasn't been expired, yet.
> Clear as mud, right?
>
> Bill Boyer
> DSS, Inc.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> kurt.beyers AT pandora DOT be
> Sent: Friday, May 16, 2003 5:40 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: delete DB2 backups and logs
>
>
> Just another thougt: the DB2 logs are archived and not backed up (if I'm
not
> mistaken? Correct me if I am). So after the value RETVAL, they are deleted
> automatically in TSM and you don't need no longer the db2adutl tool.
>
> And another question? How about the synchronization with the history log
> file? Just delete entries older than a certain time period with
>
> 'prune history timestamp with force option'
>
> Kurt
>
>
> >Hello again,
> >
> >I'm getting confused how the DB2 backups (DB2 7.1 on AIX 5.1 32bit) must
be
> >deleted in TSM (TSM server 5.1.6.3 also in AIX 5.1 32bit).
> >
> >Will the following command:
> >
> >'$db2adutl delete older than 14 days'
> >
> >delete only the full/incremental/delta backups older than 14 days or are
> the >logs that have been backed up older than 14 days also deleted?
> >
> >or do you have to delete the logs with the command:
> >
> >'$db2adutl delete logs between Sxxxxxx and Syyyyyy'
> >
> >and in that case, does somebody already have a script to determine the
> Sxxxxx >log file and Syyyyy log file. It shouldnt be too difficult but
what
> if the log >numbering returns from S9999999 to S0000000.
> >
> >A lot of theoretical questions again, but I don't have a test DB2 server
at
> >the moment where I can verify it. Thanks for any help.
>
> >Kurt
>
>
>

<Prev in Thread] Current Thread [Next in Thread>