rman备份策略制定参考内容

sky

一：在制定rman备份策略前，需对redo日志进行评估。本文按照官方文档的建议进行设置：

文档建议：

Oracle recommends that you multiplex the online redo log. The loss of log files can be catastrophic if recovery is required. When you multiplex the online redo log, the database must increase the amount of I/O it performs. Depending on your system, this additional I/O may impact overall database performance.

oracle建议使用多个redolog（如图中redo01a.log），保证redo的冗余！，并将冗余的redolog放在不同的磁盘上（图中redo01a.log放在diakA中），以减少I/O开销！

二：归档日志的配置本文参考的是：

To archive to multiple destinations, you can choose to archive to two or more locations using theLOG_ARCHIVE_DEST_n initialization parameters, or to archive only to a primary and secondary destination using theLOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST initialization parameters.

oracle还是建议使用log_archive_dest_n来配置archivelog的放置路径！而且还是遵循上的冗余策略！

注意：

If you configure a Fast Recovery Area (by setting the DB_RECOVERY_FILE_DEST andDB_RECOVERY_FILE_DEST_SIZEparameters) and do not specify any local archive destinations, the database automatically selects the Fast Recovery Area as a local archive destination and setsLOG_ARCHIVE_DEST_1 to USE_DB_RECOVERY_FILE_DEST.

如果指定了 快速恢复区（Fast Recovery Area），并且没有指定任何本地归档路径时。oracle将默认快速恢复区作为归档路径。

You must ensure that there is sufficient disk space at all times for archive log destinations. If the database encounters a disk full error as it attempts to archive a log file, a fatal error occurs and the database stops responding. You can check the alert log for a disk full message.

要确保指定的归档路径有足够的空间来存放归档日志。如果oracle在归档时发现空间不足的话，就会停止响应（挂起），在alter文件中会有提示磁盘不足的消息！

三：所以快速恢复区的大小需要dba进行估算后设置!

Use of the fast recovery area is strongly recommended. Consider configuring a fast recovery area as a first step in implementing a backup strategy
oracle强烈推荐使用快速恢复区。制定备份策略的第一步就是配置快速恢复区！

You enable the fast recovery area by setting two initialization parameters.
These parameters enable the fast recovery area without having to shut down and restart the database instance.

启用fast recovery area只需启用以下2个参数就OK了！不用重启instance

You set the size of the fast recovery area with the parameter DB_RECOVERY_FILE_DEST_SIZE first,
and then you set the physical location of the flash recovery files with the parameterDB_RECOVERY_FILE_DEST.

以下为官网上如何配置快速恢复区的大小：

The larger the fast recovery area is, the more useful it becomes. Ideally, the fast recovery area should be large enough to contain the files listed in Table 5-2. The recovery area should be able to contain a copy of all datafiles in the database and the incremental backups used by your chosen backup strategy.

If providing this much space is impractical, then it is best to create an area large enough to keep a backup of the most important tablespaces and all the archived logs not yet on tape. At an absolute minimum, the fast recovery area must be large enough to contain the archived redo logs not yet on tape. If the recovery area has insufficient space to store new flashback logs and meet other backup retention requirements, then to make room, the recovery area may delete older flashback logs.

Formulas for estimating a useful fast recovery area size depend on whether:

• Your database has a small or large number of data blocks that change frequently
  
• You store backups only on disk, or on disk and tape
  
• You use a redundancy-based backup retention policy, or a recovery window-based retention policy
  
• You plan to use Flashback Database or a guaranteed restore point as alternatives to point-in-time recovery in response to logical errors
  
  

If you plan to enable flashback logging, then the volume of flashback log generation is approximately the same order of magnitude as redo log generation. For example, if you intend to set DB_FLASHBACK_RETENTION_TARGETto 24 hours, and if the database generates 20 gigabytes of redo in a day, then a general rule of thumb is to allow 20 GB to 30 GB of disk space for the flashback logs. The same rule applies to guaranteed restore points when flashback logging is enabled. For example, if the database generates 20 GB of redo every day, and if the guaranteed restore point is kept for a day, then plan to allocate 20 to 30 GB.

Suppose that you want to determine the size of a fast recovery area when the backup retention policy is set toREDUNDANCY 1 and you intend to follow Oracle's suggested strategy of using an incrementally updated backup. In this example, you use the following formula to estimate the disk quota, where n is the interval in days between incremental updates and y is the delay in applying the foreign archived redo logs on a logical standby database:

Disk Quota =Size of a copy of database +Size of an incremental backup +Size of (n+1) days of archived redo logs +Size of (y+1) days of foreign archived redo logs (for logical standby) +Size of control file +Size of an online redo log member * number of log groups +Size of flashback logs (based on DB_FLASHBACK_RETENTION_TARGET value)

看起太复杂了 。我采用的方法是 先大楷估计oracle的数据量，合理分配一个大小。以后每天检查一次快速恢复区的大小；

SELECT * FROM V$RECOVERY_FILE_DEST; 查看快速恢复区大小

SELECT * FROM   V$RECOVERY_AREA_USAGE; 查看有那些文件

在根据备份策略来合理的进行设置大小！

如：我现在的备份策略是 基于时间窗口30天的备份策略。周末0级增备，1,2,3差异增备，4累计增备，5，6差异增备！

没开闪回数据库，归档日志在其他目录下，redo也没在快速恢复区中。

每天数据量改变不到5%。刚才我做了个全备，占用了1.5G快速恢复区大小。根据rman策略，设置大小为：10G大小。

0

我身在江湖，江湖里却没有我得传说。

zeromax

啥时硬件也可以COPY就好了!

玥殇

睡眠是一门艺术——谁也无法阻挡我追求艺术的脚步！

收入啤酒88

学习了，不错，讲的太有道理了

liyao20060101

有道理。。。

wsaer

我本非随便的人，但如果你想随便，那我就随你的便好啦！