Export a replicated MTREE to use with rman

Yes it is, only the negative is is RMAN catalog will not be aware of the replication because it will happen from one DD to Another.

To perform file replication, use a command similar to the one shown below. Edit the script

command for your environment, specifying the Data Domain system that is the

destination system for the file replication. Specifying COPIES 2 requires an installed

Replicator license on both the source and destination Data Domain systems. Making a

backup by specifying COPIES 2 requires Oracle Enterprise Edition.

Specifying COPIES 2 instructs the DD Boost RMAN plugin to perform Managed File

Replication to the second Data Domain system. The second Data Domain system name is

specified as part of the file name of the second copy. This is the 'destinationsystem'

in the command below.

The two file names specified in this command must be identical except for the inclusion

of 'destination-system' in the second name. The RMAN plugin requires that the file

names of the two copies be identical. The underscore character "_" is also required.

Omitting the underscore in the file names will result in an error and the backup will fail.

Any changes made to the file name formats shown must include an underscore character

and must guarantee that the file names are identical, except for 'destination-system'

in the name for the second copy. This means that using Oracle formats such as "%U" and

"%c" is not allowed, as these Oracle formats include the copy number in the generated

file name and thus result in the file name generated for the second copy being different

from the file name generated for the first copy.

backup copies 2 database filesperset=1 format '%u_%p', 'destination-system/%u_%p';

Note

Enter a small letter "u" in '%u_%p'. A capital "U," while a valid Oracle format, is invalid

for DD Boost RMAN and causes the replication to fail.

To use COPIES 2, the value of BACKUP_TAPE_IO_SLAVES must be TRUE, which you can

configure by entering:

SQL> show parameter backup_tape

NAME TYPE VALUE

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

backup_tape_io_slaves boolean FALSE

SQL>

SQL> alter system set backup_tape_io_slaves = true scope=spfile;

System altered.

bounce the oracle instance( shutdown and startup) the database

SQL> show parameter backup_tape

NAME TYPE VALUE

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

backup_tape_io_slaves boolean TRUE

SQL>

The only difference from performing a second backup to a different BACKUP_HOST is that

the data flow for Managed File Replication is between the two Data Domain systems. A

normal backup sends data between the backup server and a Data Domain system.

File replication must be performed to a destination storage unit with the same name as

the source storage unit. This means that the target Data Domain system must have a

storage unit that has the same name as the storage unit on the source Data Domain

system containing the file being replicated. The file will be replicated to the identically

named storage unit on the destination Data Domain system.

File replication using RMAN requires that both the source Data Domain system and the

destination Data Domain system are connected to, and accessible from, the RMAN

system performing backups. The network configuration must allow backups to both the

source Data Domain system and to the destination Data Domain system. Replication will

not work in configurations where the destination Data Domain system is only connected

to the source Data Domain system via a private network or link.

Note:

If two copies of a backup have been made using COPIES 2, during restore operations

RMAN will not automatically restore from the second backup copy if the first copy is not

available.

Thanks

Deb

  Please Like my Post if you liked it, Please Mark it as Helpful if it helped you, and mark it as Correct Answer if it resolved your query