RMAN Archive logs

[The Magnet]

Just a question about RMAN. We have the 'include archive logs'
clause in our configuration. Problem is sometimes out archive
destination location gets filled. So, I wrote a script to move them
to the RMAN location and catalog them.

I noticed something, archive logs processed by the normal RMAN process
have a backup piece name: arc_03282011_NI00_110018.

But if I move it and catalog it, it still has the normal archive log
name: arch_1_141388.638873632.arc

Is this a problem? What does the 'include archive logs' clause do? I
thought that included the logs in the backup piece itself and the
actual log was no longer needed.

[Mladen Gogala]

Just a question about RMAN. We have the 'include archive logs' clause
in our configuration. Problem is sometimes out archive destination
location gets filled. So, I wrote a script to move them to the RMAN
location and catalog them.

Well, in Oracle 11g there is a brand new option which enables you to say
"BACKUP ARCHIVELOG UNTIL TIME 'SYSDATE - 1/48' DELETE INPUT" or,
alternatively,
"BACKUP ARCHIVELOG ALL DELETE ALL INPUT"

Rumors are that in version 12g of Oracle it will be possible to do
something like
"BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL DELETE INPUT"

If your rman is connected to the catalog, the backup of those deleted
archivelog will be automagically cataloged.

[John Hurley]

The Magnet:

# Problem is sometimes out archive destination location gets filled.

You are not using some kind of pro active monitoring and knowing/
predicting when your mount points or archive log destinations are
going to fill up well before it happens?

It is easy enough to script out monitoring solutions on any recent
platforms unix/linux even windows.

I would start with getting something like this setup first before
exploring the rman implications personally.

If you need to move things around when mount points come under space
pressure you can also script that out. One alternative is keeping
rman informed of where you have moved things another alternative is
hiding them from rman ... if you hide them better do cross checks to
let rman know that they have ( at least temporarily ) gone missing.

[Mladen Gogala]

The Magnet and, at one time dbaplusplus are my favorite targets. They
never read the manuals.

[Sybrand Bakker]

On Tue, 5 Apr 2011 23:50:14 +0000 (UTC), Mladen Gogala

Post by Mladen Gogala
The Magnet and, at one time dbaplusplus are my favorite targets. They
never read the manuals.

How about zigzagdna?
Posts all of his questions both here and on OTN!!!

------
Sybrand Bakker
Senior Oracle DBA

[Mladen Gogala]

Post by Sybrand Bakker
How about zigzagdna?
Posts all of his questions both here and on OTN!!!

I stand corrected. Zigzagdna, too, belongs to the same category.

[Hemant K Chitale]

CATALOGing the ArchiveLog does NOT mean that it is backed up ! The
archivelog remains "in place". You have to explicitly run a BACKUP
ARCHIVELOG .... command.

The "arc_...." name follows from the FORMAT that you have specified in
the BACKUP command.

(and when you say "include archivelog", I believe that you mean "plus
archivelog").

Post by The Magnet
I noticed something, archive logs processed by the normal RMAN process
have a backup piece name:  arc_03282011_NI00_110018.
But if I move it and catalog it, it still has the normal archive log
name:  arch_1_141388.638873632.arc

Hemant K Chitale