Home > Oracle in general > RMAN in Data Guard configurations – Problems of restoring rman disk backups and standby site and vice versa

RMAN in Data Guard configurations – Problems of restoring rman disk backups and standby site and vice versa

… or: the problem of backup association

From time to time i come across the same problems in data guard configurations using rman-to-disk: Backups taken on the standby database are not taken into account when trying to perform an rman recovery on the primary site and vice versa.

This is an expected behavior according to the oracle documentation:

The accessibility of a backup is different from its association. In a Data Guard environment, the recovery catalog considers disk backups as accessible only to the database with which it is associated, whereas tape backups created on one database are accessible to all databases. If a backup file is not associated with any database, then the row describing it in the recovery catalog view shows null for the SITE_KEY column. By default, RMAN associates files whose SITE_KEY is null with the database to which it is connected as TARGET.

RMAN commands such as BACKUP, RESTORE, and CROSSCHECK work on any accessible backup. For example, for a RECOVER COPY operation, RMAN considers only image copies that are associated with the database as eligible to be recovered. RMAN considers the incremental backups on disk and tape as eligible to recover the image copies. In a database recovery, RMAN considers only the disk backups associated with the database and all files on tape as eligible to be restored.

To illustrate the differences in backup accessibility, assume that databases prod and standby1 reside on different hosts. RMAN backs up datafile 1 on prod to /prmhost/disk1/df1.dbf on the production host and also to tape. RMAN backs up datafile 1 on standby1 to /sbyhost/disk2/df1.dbf on the standby host and also to tape. If RMAN is connected to database prod, then you cannot use RMAN commands to perform operations with the /sbyhost/disk2/df1.dbf backup located on the standby host. However, RMAN does consider the tape backup made on standby1 as eligible to be restored.

Note: This is a quote from the 11g R1 documentation. The same text apprears in 10g R2 documentation as well.

Categories: Oracle in general Tags:
  1. October 9th, 2009 at 17:54 | #1

    Your blog is so informative ‚Ķ ..I just bookmarked you….keep up the good work!!!!

  2. October 9th, 2009 at 19:03 | #2

    Generally I do not post on blogs, but I would like to say that this post really forced me to do so, Excellent post!

  3. S Cole
    July 14th, 2012 at 16:13 | #3

    I only found this ‘feature’ with > 10gR2 – that release and lower seems to work ‘as expected’ (backups taken on the standby can be restored seamlessly to the primary and vice versa)

    There is a work-around for > 11gR1, from RMAN:

    RMAN> set backup files for device type disk to accessible;

    Does the trick

    We ended up raising this, and getting the documentation updated… Support note 1070039.1 tells all.

  1. No trackbacks yet.