Reference for RMAN backup policy formulation

Redo logs must be evaluated before the rman backup policy is developed. We recommend that you use multiple redologs (in redo01a. log) in oracle to ensure redo redundancy !, And redundant

Redo logs must be evaluated before the rman backup policy is developed. We recommend that you use multiple redologs (in redo01a. log) in oracle to ensure redo redundancy !, And redundant

I. Before formulating the rman backup policy, redo logs should be evaluated. This article is based on the recommendations in the official documentation:

Documentation recommendations:

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.

We recommend that you use multiple redologs (in redo01a. log) in oracle to ensure redo redundancy !, And put redundant redolog on different disks (in the figure, redo01a. log is placed in diakA) to reduce I/O overhead!

Ii. configuration of archiving logs:

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

We recommend that you use log_archive_dest_n in oracle to configure the archivelog placement path! In addition, we still follow the redundancy policy!

Note:

If you configure a Fast reify Area (by setting the DB_RECOVERY_FILE_DEST andDB_RECOVERY_FILE_DEST_SIZE parameters) 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.

If a Fast Recovery Area is specified and no local archiving path is specified. Oracle uses the default quick recovery area as the archive path.

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.

Make sure that the specified archiving path has enough space to store archived logs. If oracle finds insufficient space during archiving, it will stop responding (suspended). A message indicating insufficient disk is displayed in the alter file!

,