Well put.
Consider also that if a given block is modified many times, then the size of
the deltas in the redo stream likely exceeds the size of the one current
version of the block that will need to be written to the incremental backup and
applied in the course of rolling forward from the full backup through any
incrementals.
Having the two possible recovery scenarios might allow you to minimize the
recovery time depending on the texture of updates to your database.
mwf
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Sandra Becker
Sent: Friday, November 13, 2015 2:10 PM
To: Brian.Zelli@xxxxxxxxxxxxxxx
Cc: oracle-l (oracle-l@xxxxxxxxxxxxx)
Subject: Re: diff between incremental and archive backups
Depending on how many archivelogs your database writes in a week, that could be
a lot of logs to apply. Consider if you have the space to store them, or time
to restore them to disk, and the time to apply all the logs vs. doing
incremental backups and applying fewer logs. Just something to consider.
Sandy B.
On Fri, Nov 13, 2015 at 11:59 AM, Zelli, Brian <Brian.Zelli@xxxxxxxxxxxxxxx>
wrote:
So we were having a discussion about rman incremental backups. And the
question came up that if I do an rman full once a week and then rman back up of
the archive logs the rest of the week, that’s all I need to do a point in time
restore. I don’t have to do incremental backups. Is this an accurate
assumption?
Brian
This email message may contain legally privileged and/or confidential
information. If you are not the intended recipient(s), or the employee or agent
responsible for the delivery of this message to the intended recipient(s), you
are hereby notified that any disclosure, copying, distribution, or use of this
email message is prohibited. If you have received this message in error, please
notify the sender immediately by e-mail and delete this email message from your
computer. Thank you.
--
Sandy B.