RE: Documentation for reasons to NOT use RAC?
Date: Mon, 22 Feb 2010 13:45:47 -0500
True, but in my case I deal with multi-terabyte databases that can take 8-16 hours to backup via RMAN with a single stream to disk. Moving to 4 or 8, or even 32 streams can cut this time dramatically- in this case down to 90 minutes. This was very true on a Sun T5220 that had a small user base (data warehouse) but a large database, using RMAN to disk.
Like anything, "it depends" is the correct answer here :) Interesting enough I have never used the disk staging facility of Netbackup, but I hear good things about it.
From: Allen, Brandon [mailto:Brandon.Allen_at_OneNeck.com] Sent: Monday, February 22, 2010 1:27 PM
To: Crisler, Jon; oracle-l_at_freelists.org Subject: RE: Documentation for reasons to NOT use RAC?
Just something else to consider on that topic - a single stream can move data pretty quickly if you are using async IO, and backing up to disk instead of tape, either via regular disk backup, e.g. to your flash recovery area, or through sbt_tape to a disk staging unit used by your Media Management software (e.g. Netbackup) before it actually writes to tape.
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Crisler, Jon
If you must have RAC, then also consider Oracle RAC Standard Edition (as
opposed to Enterprise).
. . .
Just make sure you can live without the certain features it omits- for large databases just the fact that RMAN is limited to a single stream can be a deal-breaker.
Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it.Received on Mon Feb 22 2010 - 12:45:47 CST