Which two restrictions apply when the RMAN BACKUP AS COPY command is used to create a backup?

Question

Options

• ABackups can be taken only if a fast recovery area is configured.
• BBackups can be written only to disk.
• CBackups can be taken only for data files.
• DBinary compression cannot be applied to the backup.
• EBackups can be written only if checksums are stored for each block.
• FBackups can be written only to media.

• B
  88% (43)
• C
  4% (2)
• E
  2% (1)
• F
  6% (3)

Explanation

RMAN BACKUP AS COPY creates image copies - bit-for-bit duplicates of files - which imposes two hard restrictions.

Why B and D are correct: Image copies must be written to disk only; they cannot be sent to tape or any SBT (System Backup to Tape) media channel (B). Because image copies are exact file duplicates, binary compression cannot be applied - compression is a feature exclusive to backup sets, not image copies (D).

Why the distractors are wrong:

• A - A fast recovery area is not required; image copies can be placed in any valid disk location.
• C - BACKUP AS COPY works on data files, control files, and archived redo logs - not data files alone.
• E - Block checksums have no bearing on whether a copy can be written; they are independent of the backup method.
• F - This is the opposite of B; image copies go to disk, not media/tape.

Memory tip: Think of BACKUP AS COPY as a simple cp command - you can only copy a file to local disk, and you can't compress it mid-copy. If you need tape or compression, use BACKUP AS BACKUPSET instead.

No community discussion yet for this question.