Like the previous responder said, the retention of the redo logs are controlled 
by RMAN and not Netbackup.  Have the DBA's change the retention of the RMAN 
backups to match their requirement if a hot backup is the only way you can 
backup the data.

If you can bring down the database so that there are no open tables or 
transactions being performed, you can perform a full cold backup of all the 
required filesystems inside Netbackup and then set the retention of that backup 
to match the new requirements.  One thing to note here is that in order for you 
to capture all the files required to restart the database from this backup, you 
will need to make sure that any files currently excluded from your OS backups 
(such as redo logs, dbf's etc..) are not excluded in your cold backup.  Your 
DBA's should know which files they'll need and which ones they won't.

Mark Glazerman
Desk: 314-889-8282
Cell: 618-520-3401
 please don't print this e-mail unless you really need to

-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu 
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of jjperry
Sent: Wednesday, September 22, 2010 2:08 PM
To: VERITAS-BU AT MAILMAN.ENG.AUBURN DOT EDU
Subject: [Veritas-bu] Oracle hot backup with yearly retention: redo logs?


robmod wrote:
> Hello everybody, 
> we have many oracle instances in archivelog mode. We keep archivelogs for 30 
> days.
> Now we have to backup some oracle instance only with full hot backups with 
> long retention (up to 3 years). As oracle man says redo logs are needed for 
> restore, so we have to change the retention of the archivelogs created during 
> long retention hot backup. 
> How would you backup oracle in this way?


I would suggest that you take a look at 
http://www.symantec.com/business/support/index?page=content&id=TECH49868 as a 
possible reference.  While this pertains mostly to NetBackup, the RMAN 
information on retentions should be independent of the backup product used as 
it resides in the RMAN setup.

From reading the article, not using RMAN myself as that is relegated to the 
DBAs, it would seem that you would have to change the retention on all backup 
in RMAN to support just the yearly backups you need to keep.  

Another way I would suggest that might possibly work is to backup the database 
offline for the yearly backup instead of the hot backup as it should not 
require the archive logs at that point, at least it seems that you would not 
need them with the DB down.

+----------------------------------------------------------------------
|This was sent by jjperry AT water DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu