There are a couple of distinct
advantages for using RMAN to perform image copy backups: First, the backup is automatically
recorded in the RMAN repository. Second, all blocks are checked for corruption as they are read
and copied to the backup destination. Another side benefit to making image copies is that the
copies can be used ???as is??? outside of RMAN if, for some reason, a recovery operation must occur
outside of RMAN.
In the example that follows, we make another backup of the INET_STAR tablespace, this time
as an image copy:
FIGURE 12-7 Tablespace backup files in OEM
Chapter 12: Using Recovery Manager (RMAN) 443
RMAN> backup as copy tablespace inet_star;
Starting backup at 30-AUG-07
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile copy
input datafile file number=00007
name=+DATA/dw/datafile/inet_star.268.632004213
output file name=+RECOV/dw/datafile/inet_star.304.632005047
tag=TAG20070830T205713 RECID=2 STAMP=632005118
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:01:14
Finished backup at 30-AUG-07
Starting Control File and SPFILE Autobackup at 30-AUG-07
piece handle=+RECOV/dw/autobackup/2007_08_30/
s_632005123.305.632005135 comment=NONE
Finished Control File and SPFILE Autobackup at 30-AUG-07
RMAN>
Image copies can only be created on DISK device types. In Figure 12-8, we perform the same
backup with OEM.
Because we had earlier configured the default backup type to compressed backupset, we
overrode the default value in an earlier setup screen for this backup.
Pages:
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685