Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Backup trends (2): HOT or COLD
Joel Garry wrote:
> Lucyna Witkowska <ypwitkow_at_nospamcyf-kr.edu.pl> wrote in message news:<c5omr6$n60$1_at_srv.cyf-kr.edu.pl>...
>
>>Hi, >>Thank you very much for all answers and especcially Denis for his hints. >>
Finally in 10g I find the feature that was most lacking in previous versions of RMAN (from the release notes):
"Binary Compression of Backup Sets
RMAN can now write backup sets in a format that uses binary compression
to reduce backup set size. Using compressed backup sets can save storage
space, as well as network bandwidth when backing up across a network."
I inherited a well-written Unix hot backup shell script that has served excellently through upgrades from 8.1.5 to 8.1.6 to 9.2.0, Solaris and Linux, almost no maintenance required. And it compressed the files! If not, I would have used RMAN instead.
Second-worst problem was the ease of "cloning" a database, which was answered earlier in this thread. I figured it out eventually on my own several years ago, but the clunkiness of it left a very bad taste in my mouth.
Third, it is interesting to note that Oracle has published a "RMAN Myths Dispelled" document on Metalink (Note:134214.1). I don't think they ever had to publish a "Hot backup myths dispelled" document. ;-)
Here is an excerpt:
Myth #1. RMAN only backs up those datablocks which contain data.
Myth #2: Incremental backups will take significantly less time to backup
than full backups.
Myth #3: I can specify incremental backups during a restore operation.
--Mark Bole Received on Wed May 05 2004 - 20:28:00 CDT