rman 与 data guard 的问题

lfree

问一个rman的问题，我现在使用rman备份：
我隔一定的时间执行如下：

delete noprompt obsolete  until time 'sysdate-60'  ;

问一下如果删除了archive log文件，data guard机器 由于各种原因中断了或者停在某个地方，
许多的archive log没有办法获得，data guard如何处理，重做吗？

另外问一下，有什么机制能够避免这个问题的发生。

谢谢！

junsansi

我认为，恐怕只能重做了~~

最好的方式，当然是把备份放到standby端执行喽

lfree

我想知道的是rman是否有什么机制，可以做到没有standby的，依旧保留。

因为前几天我们data guard的磁盘满了，我没有注意，当然archive log还在。

lfree

顶上来。
我想在做删除的时候，rman是否有某种机制保障没有做standby的不删除。

谢谢！

shooterchan

原帖由 lfree 于 2008-3-21 08:29 发表
顶上来。
我想在做删除的时候，rman是否有某种机制保障没有做standby的不删除。

谢谢！

根据v$archived_log的applied字段判断日志是否该删除。
如果是10g的，还可以设置
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;

terry_wu040802

我怎么记得是：
archive log 默认是不会被删除的，如果你的standby没有apply log的话？

lfree

谢谢！
不过看$archived_log是否有些乱。

jieyancai

Subject:  RMAN backups in Max Performance/Max Availability Data Guard Environment
  Doc ID:  Note:331924.1 Type:  BULLETIN
  Last Revision Date:  28-DEC-2007 Status:  PUBLISHED

In this Document
  Purpose
  Scope and Application
  RMAN backups in Max Performance/Max Availability Data Guard Environment
  References



--------------------------------------------------------------------------------



Applies to:
Oracle Server - Enterprise Edition - Version: 10.1 to 10.2
Information in this document applies to any platform.

Purpose
When using 'configure archive log deletion policy to applied on standby' on primary database, allow RMAN to consider *both* mandatory and optional destinations when determining which logs on primary can be deleted.

Scope and Application
RMAN backups on standby database in Data Guard environment
RMAN backups in Max Performance/Max Availability Data Guard Environment
The 10g RMAN-Data Guard paper states that 'archive log deletion policy applied on standby' only checks that a log has been applied on all mandatory standby databases.
However, Data Guard best practice for Max Performance and Max Availability modes is to *not* use mandatory standby (so that primary does not hang in the event of online logs filling up). Therefore, the following parameter must be set:

_log_deletion_policy='ALL'

This will allow RMAN to delete logs from the Flash Recovery Area on primary database host that have been applied to all standby databases (whether mandatory or optional). Database will require bounce after setting this parameter.

NOTE:  To make the change in an spfile, double quotes must be used around parameter name:

alter system set "_log_deletion_policy"=ALL scope=spfile sid='*';

NOTE: attempt to set this configuration in RMAN without this parameter setting may result in error:

RMAN> configure archivelog deletion policy to applied on standby;

new RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN-08591: WARNING: invalid archivelog deletion policy


References
Bug 5261960 - RMAN-8591 STANDBY DESTIONATION MUST BE MANDERATORY WHILE MAX PERFORMANCE

Errors
RMAN-8591 WARNING: invalid archivelog deletion policy

[ 本帖最后由 jieyancai 于 2008-3-21 09:10 编辑 ]

jieyancai

另外可以先试试：
Examples of the CONFIGURE ARCHIVELOG DELETION POLICY Command
When backups of archived redo log files are taken on the standby database:

Issue the following command on the primary database:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;


Issue the following command on the standby database:
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;


When backups of archived redo log files are taken on the primary database:

Issue the following command on the standby database:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;


Issue the following command on the primary database:
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;

lfree

谢谢！这个正是我需要的，我再认真看看先。