Re: RMAN incrementally updated image copy as a long term backup solution?
- From: Randal Bennett <rdbennett2000@xxxxxxxxx>
- To: "oracle.unknowns@xxxxxxxxx" <oracle.unknowns@xxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 29 Nov 2012 17:21:57 -0800 (PST)
Chen,
Para 16.1.2.1 of the Oracle v11g online reference says:
If you use RMAN with the following configuration when backing up or
restoring files, then it detects all types of block corruption that are
possible to detect:
* In the initialization parameter file of a database, set
DB_BLOCK_CHECKSUM=typical so that the database calculates data file checksums
automatically (not for backups, but for data files in use by the database)
* Do not precede the BACKUP command with SET MAXCORRUPT so that RMAN
does not tolerate any unmarked block corruptions.
* In a BACKUP command, do not specify the NOCHECKSUM option so that
RMAN calculates a checksum when writing backups
* In BACKUP and RESTORE commands, specify the CHECK LOGICAL option so
that RMAN checks for logical and physical corruptionHTH
-- Randy
________________________________
From: Chen Zhou <oracle.unknowns@xxxxxxxxx>
To: oracle-l@xxxxxxxxxxxxx
Sent: Wednesday, November 28, 2012 10:10 PM
Subject: RMAN incrementally updated image copy as a long term backup solution?
Hi,
We are considering to use RMAN image copy as our backup method, then apply
the daily incrementals to update the image copy. Has anyone done that
before? If the image copy is corrupted, will it be picked up when the
daily incremental is applied? Or we need to run validate periodically on
the copy?
Thank you,
Chen
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
