I wouldn't touch this with a sharp stick, but the way to do it isn't that
hard.

Set up a different init<SID>.utl file with the proper management class for
the retention and invoke brbackup with the -r <path to init<SID>.utl file>
parameter. Run this from cron -- best bet is a nice backup script, with an
indication it's being run as the monthly or annual. For the annuals (and
maybe the monthlys) I'd also want to archive to the same management class
/sapmnt/<SID> and /oracle/<SID> -- all the executables of both SAP and
oracle and any other files that might be needed 6 years from now to bring
the system back up. Which is why I wouldn't touch it here :-)

These are obviously all off-line backups, or you've been signed up to keep
the offline redo logs for seven years.

Tom Kauffman
NIBCO, Inc

> -----Original Message-----
> From: Paul Fielding [mailto:paul AT MAINLAND DOT CA]
> Sent: Monday, April 29, 2002 12:23 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: TDP R3 keeping monthly and yearly for different retentions?
>
>
> Hi all,
>
> I did some poking around the list and didn't see anything on
> the subject.
>
> Does anybody have a good method for doing Monthly and Yearly
> backups of an R3 (oracle) database using the TDP for R3? I
> have a requirement to maintain daily backups for 2 weeks,
> monthly backups for 3 months and yearly backups for 7 years.
>  Superficially, It appears to be straightforward to set up
> different server stanzas within the TDP profile for different
> days of the week, but that's it.
>
> I suspect that I could get extra fancy and write a script to
> do a flip of the profile to an alternate profile file on the
> appropriate days, and have it flip back when it's done, but
> that seems like a bit of a band-aid to me and I'm wondering
> if anyone's come up with something better?
>
> regards,
>
> Paul
>