Mike_Hoskins
13 years agoLevel 2
RMAN Settings for Dedup
I'm working on adjusting filesperset for our Oracle RMAN backup script. The filesperset at 1 for the data files makes perfect sense. This will grow the catalog but the average size of the data involved and the unchanging nature of the majority in most tables makes this at least palitable.
Then on the archived redo logs there seems to be differing thoughts. First is to also set this to 1. For max dedup again this makes sense. If the database is very busy this will grow the catalog dramatically, possibly to unacceptable levels. The other side of the coin is to go as high as 20 in some examples. Because of the transient nature of redo logs will only be archived so many times. I have read "since they don't dedup well" - maybe this is what that refers to? The log itself won't change obviously. But data files are generally long-lived structures.
Thoughts? Did I miss something obvious?